How severe is GHSA-9jr9-8ff3-m894?

GHSA-9jr9-8ff3-m894 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9jr9-8ff3-m894?

GHSA-9jr9-8ff3-m894 affects the following packages: @haxtheweb/haxcms-nodejs (npm), elmsln/haxcms (Packagist). Ecosystems affected: npm, Packagist.

How do I fix GHSA-9jr9-8ff3-m894?

Update @haxtheweb/haxcms-nodejs to 11.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jr9-8ff3-m894 is resolved across your whole dependency graph.

How do I detect GHSA-9jr9-8ff3-m894 in my npm, Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @haxtheweb/haxcms-nodejs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9jr9-8ff3-m894 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-9jr9-8ff3-m894?

O3 pinpoints whether GHSA-9jr9-8ff3-m894 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9jr9-8ff3-m894 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9jr9-8ff3-m894 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9jr9-8ff3-m894?

GHSA-9jr9-8ff3-m894 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-9jr9-8ff3-m894 published, and has it been updated?

GHSA-9jr9-8ff3-m894 was published on July 25, 2025 and was last updated on July 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm🐘 Packagist

GHSA-9jr9-8ff3-m894

HIGH

HAX CMS API Lacks Authorization Checks

Also known asCVE-2025-54378

Published

Jul 25, 2025

Updated

Jul 28, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk36th percentile+0.11%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

📦@haxtheweb/haxcms-nodejs🐘elmsln/haxcms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm, Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Make a POST request to the 'deleteNode' endpoint with a valid JWT and the target object ID.

Site before editing:

Site after editing:

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@haxtheweb/haxcms-nodejs`	all versions	11.0.14
🐘Packagist	`elmsln/haxcms`	all versions	11.0.14

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @haxtheweb/haxcms-nodejs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @haxtheweb/haxcms-nodejs to 11.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jr9-8ff3-m894 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9jr9-8ff3-m894 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9jr9-8ff3-m894. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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](https://github.com/haxtheweb/haxcms-php/blob/b158d8ba1f9602af92ab084fd03b418f953079fd/system/backend/php/lib/Operations.php#L760) `c

O3 Security · Impact-Aware SCA

Is GHSA-9jr9-8ff3-m894 in your dependencies?

O3 detects GHSA-9jr9-8ff3-m894 across npm, Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works