8.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-54378

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.

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:

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-54378

CVE-2025-54378:

8.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
@haxtheweb/haxcms-nodejs	npm	< 11.0.14	11.0.14
elmsln/haxcms	composer	< 11.0.14	11.0.14

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the HAX CMS API endpoints, which fail to perform authorization checks before executing operations on resources. This affects both the Node.js and PHP versions of the CMS. While the API checks for user authentication (i.e., if a user is logged in), it does not verify if the authenticated user has the necessary permissions to perform the requested action on a specific resource (e.g., a site or a node). This allows any authenticated user to perform actions on any site or node within the CMS, even those belonging to other users.

The analysis of the provided patch for the Node.js version (@haxtheweb/haxcms-nodejs) confirms this. The patch consistently adds authorization checks using HAXCMS.validateRequestToken to various API route handlers. For example, in src/routes/deleteNode.js, the patch adds a condition to check for a valid site_token before allowing the deletion of a node. The vulnerable functions are the route handlers in the src/routes directory that were modified to include these checks.

Similarly, the vulnerability description explicitly lists several methods within the Operations.php file of the PHP version (elmsln/haxcms) as being affected. These methods, such as createNode(), deleteNode(), and cloneSite(), lack the necessary authorization logic, making them vulnerable.

An attacker can exploit this vulnerability by authenticating to the application and then sending API requests with the identifiers of other users' sites or nodes. This can lead to unauthorized enumeration, modification, or deletion of content, and in the case of the getConfig or getUserData endpoints, the potential leakage of sensitive configuration data.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.