CVE-2025-54378: HAX CMS API Lacks Authorization Checks
Summary The HAX CMS API endpoints do not perform authorization checks when interacting with a resource. Both the JS and PHP versions of the CMS do not verify that a user has permission to interact with a resource before performing a given operation. Details The API endpoints within the HAX CMS application check if a user is authenticated, but don't check for authorization before performing an operation.
Published Jul 25, 2025 · Updated Jul 28, 2025
Affected packages
@haxtheweb/haxcms-nodejs
- Ecosystem
- npm
- Affected
- < 11.0.14
- Fixed in
- 11.0.14
- Check
npm ls @haxtheweb/haxcms-nodejs
elmsln/haxcms
- Ecosystem
- Composer (PHP)
- Affected
- < 11.0.14
- Fixed in
- 11.0.14
- Check
composer show elmsln/haxcms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The HAX CMS API endpoints do not perform authorization checks when interacting with a resource. Both the JS and PHP versions of the CMS do not verify that a user has permission to interact with a resource before performing a given operation.
Details
The API endpoints within the HAX CMS application check if a user is authenticated, but don't check for authorization before performing an operation.
Affected Resources
- Operations.php: 760
createNode() - Operations.php: 868
saveNode() - Operations.php: 1171
deleteNode() - Operations.php: 1789
listSites() - Operations.php: 1890
createSite() - Operations.php: 2196
getConfig() - Operations.php: 2389
cloneSite() - Operations.php: 2467
deleteSite() - Operations.php: 2524
downloadSite() - Operations.php: 2607
archiveSite()
_Note: This may not include all affected endpoints within the application._
Impact
An authenticated attacker can make requests to interact with other users' sites. This can be used to enumerate, modify, and delete other users' sites and nodes.
Additionally, an authenticated attacker can use the 'getConfig' endpoint to pull the application's configuration, which may store cleartext credentials.
PoC - /deleteNode
- Browse to the 'site.json' file for a target site, and note the ID of the item to delete.
image
- Make a POST request to the 'deleteNode' endpoint with a valid JWT and the target object ID.
image
Site before editing:
image
Site after editing:
image
Credited to lfgberg.
References
- https://github.com/haxtheweb/issues/security/advisories/GHSA-9jr9-8ff3-m894
- https://github.com/haxtheweb/haxcms-nodejs/commit/5826e9b7f3d8c7c7635411768b86b199fad36969
- https://nvd.nist.gov/vuln/detail/CVE-2025-54378
- https://github.com/haxtheweb/haxcms-php/commit/24d30222481ada037597c4d7c0a51a1ef7af6cfd
- https://github.com/advisories/GHSA-9jr9-8ff3-m894
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-48527
HaxCMS has a stored Cross-Site Scripting (XSS) bypass in its saveNode endpoint
high8.7May 29, 2026CVE-2026-46357
HAX CMS: Denial of Service using Malicious Import Request
medium6.5May 19, 2026CVE-2026-46393
HAXcms createSite SSRF Enables Arbitrary File Read
high7.1May 19, 2026CVE-2026-46395
HAXcms: Private Key Disclosure via Broken HMAC Implementation
critical9.3May 19, 2026CVE-2026-46396
Stored XSS via <iframe> in HAX CMS allows access to sensitive client-side data and account takeover
high8.6May 19, 2026CVE-2026-46496
HAX CMS: Stored XSS via '<video-player>' component allows arbitrary JavaScript execution and token theft
medium5.1May 19, 2026
