{"answers":{"affected":"2 open source packages ship an affected version, including @haxtheweb/haxcms-nodejs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-54137 in the wild and no public exploit code.","fix":"Upgrade @haxtheweb/haxcms-nodejs to 11.0.10 or later.","what":"CVE-2025-54137 is a high-severity vulnerability in haxtheweb issues, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54137 and fix it if it is affected.\n\nWhat it is: CVE-2025-54137 is a high-severity vulnerability in haxtheweb issues, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-54137 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @haxtheweb/haxcms-nodejs (npm): affected all versions; fixed in 11.0.10\n- @haxtheweb/haxcms-nodejs (npm): affected all versions; fixed in 11.0.10\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-54137/ (Markdown: https://insights.sbomify.com/CVE-2025-54137/index.md)","id":"CVE-2025-54137","markdown":"https://insights.sbomify.com/CVE-2025-54137/index.md","name":"CVE-2025-54137","record":{"aliases":["GHSA-5fpv-5qvh-7cf3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"HAX CMS NodeJS","requires_auth":"none","summary":"Unauthenticated attackers can use hardcoded default credentials and JWT keys to access and modify HAX CMS instances.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"haxcms-nodejs","vendor":"psu"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-1392","name":"Use of Default Credentials"}],"description":"HAX CMS NodeJS allows users to manage their microsite universe with a NodeJS backend. Versions 11.0.9 and below were distributed with hardcoded default credentials for the user and superuser accounts. Additionally, the application has default private keys for JWTs. Users aren't prompted to change credentials or secrets during installation, and there is no way to change them through the UI. An unauthenticated attacker can read the default user credentials and JWT private keys from the public haxtheweb GitHub repositories. These credentials and keys can be used to access unconfigured self-hosted instances of the application, modify sites, and perform further attacks. This is fixed in version 11.0.10.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NodeJS version of the HAX CMS application is distributed with Default Secrets","id":"CVE-2025-54137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"LibreNMS has Authenticated Local File Inclusion in ajax_form.php that Allows RCE","id":"CVE-2025-54138"},"packages":[{"ecosystem":"npm","fixed":["11.0.10"],"introduced":["0"],"last_affected":[],"package":"@haxtheweb/haxcms-nodejs","purl":null,"source":"GHSA-5fpv-5qvh-7cf3"},{"ecosystem":"npm","fixed":["11.0.10"],"introduced":["0"],"last_affected":[],"package":"@haxtheweb/haxcms-nodejs","purl":"pkg:npm/%40haxtheweb/haxcms-nodejs","source":"GHSA-5fpv-5qvh-7cf3"}],"prev":{"headline":"Cursor's Modification of MCP Server Definitions Bypasses Manual Re-approvals","id":"CVE-2025-54136"},"products":["issues"],"published":"2025-07-22","related":[{"cvss_score":9.3,"headline":"HAXcms's Insecure Default Configuration Leads to Unauthenticated Access","id":"CVE-2025-54127","kev_date_added":null,"published":"2025-07-21"},{"cvss_score":8.6,"headline":"HaxCMS-PHP Command Injection Vulnerability","id":"CVE-2025-49141","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.5,"headline":"Hax CMS Stored Cross-Site Scripting vulnerability","id":"CVE-2025-49137","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.3,"headline":"HAX CMS Backend Lacks Comprehensive Authorization Checks","id":"CVE-2025-54378","kev_date_added":null,"published":"2025-07-26"},{"cvss_score":8.1,"headline":"HAXcms Has Stored XSS Vulnerability that May Lead to Account Takeover","id":"CVE-2026-22704","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":7.2,"headline":"HAX CMS NodeJs's Disabled Content Security Policy Enables Cross-Site Scripting","id":"CVE-2025-54128","kev_date_added":null,"published":"2025-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-23","vendors":["haxtheweb"]},"summary":"Unauthenticated attackers can use hardcoded default credentials and JWT keys to access and modify HAX CMS instances.","url":"https://insights.sbomify.com/CVE-2025-54137/"}