Advisory

GHSA-hxrr-x32w-cg8g

Also known as: CVE-2025-49138

Summary

HAX CMS vulnerable to Local File Inclusion via saveOutline API Location Parameter

Details

Summary
An authenticated Local File Inclusion (LFI) vulnerability in the HAXCMS saveOutline endpoint allows a low-privileged user to read arbitrary files on the server by manipulating the location field written into site.json. This enables attackers to exfiltrate sensitive system files such as /etc/passwd, application secrets, or configuration files accessible to the web server (www-data).

Details
The vulnerability stems from the way the HAXCMS backend handles the location field in the site's outline. When a user sends a POST request to /system/api/saveOutline, the backend stores the provided location value directly into the site.json file associated with the site, without validating or sanitizing the input.

Later the location parameter is interpreted by the CMS like in HAXCMSSite.php line 1248 to resolve and load the content for a given node. If the location field contains a relative path like ../../../etc/passwd, the application will attempt to read and render that file.

PoC

  1. Authenticate to the CMS and retrieve the JWT and CSRF token.
  1. Issue a POST request to /system/api/saveOutline with the path traversal injection via the location parameter :

<img width="839" alt="LFI" src="https://github.com/user-attachments/assets/91b1bb7f-9248-40d2-81fc-f839beb4d39c" />

  1. Curl the website root to see the file contents.

passwd

Impact
This is an authenticated Local File Inclusion (LFI) vulnerability, via the location parameter the attacker can read any file on the filesystem that is accessible by the www-data user.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-06-09 17:47 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

elmsln/haxcms

Packagist · All systems

Affected

  • introduced 0, fixed 11.0.0 (ecosystem)

Fixed versions

11.0.0

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences