{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54129 exists.","fix":"No fix has been published for CVE-2025-54129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54129 is a medium-severity vulnerability in haxtheweb issues, published on 21 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54129 and fix it if it is affected.\n\nWhat it is: CVE-2025-54129 is a medium-severity vulnerability in haxtheweb issues, published on 21 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54129 exists.\n\nAffected product: haxtheweb issues. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-54129/ (Markdown: https://insights.sbomify.com/CVE-2025-54129/index.md)","id":"CVE-2025-54129","markdown":"https://insights.sbomify.com/CVE-2025-54129/index.md","name":"CVE-2025-54129","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"HAXiam CMS wrapper","requires_auth":"low_privilege","summary":"An authenticated attacker can enumerate valid user accounts by observing HTTP response codes, facilitating targeted attacks against the HAXiam platform.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"haxiam","vendor":"psu"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"HAXiam is a packaging wrapper for HAXcms which allows anyone to spawn their own microsite management platform. In versions 11.0.4 and below, the application returns a 200 response when requesting the data of a valid user and a 404 response when requesting the data of an invalid user. This can be used to infer the existence of valid user accounts. An authenticated attacker can use automated tooling to brute force potential usernames and use the application's response to identify valid accounts. This can be used in conjunction with other vulnerabilities, such as the lack of authorization checks, to enumerate and deface another user's sites. This is fixed in version 11.0.5.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"HAXiam allows for User Enumeration","id":"CVE-2025-54129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cursor Agent is vulnerable prompt injection via Editor Special Files","id":"CVE-2025-54130"},"packages":[],"prev":{"headline":"HAX CMS NodeJs's Disabled Content Security Policy Enables Cross-Site Scripting","id":"CVE-2025-54128"},"products":["issues"],"published":"2025-07-21","related":[{"cvss_score":8.7,"headline":"HAX CMS's public /server-status endpoint exposes authentication tokens, user activity, and client IP addresses","id":"CVE-2026-35185","kev_date_added":null,"published":"2026-04-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-22","vendors":["haxtheweb"]},"summary":"An authenticated attacker can enumerate valid user accounts by observing HTTP response codes, facilitating targeted attacks against the HAXiam platform.","url":"https://insights.sbomify.com/CVE-2025-54129/"}