{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52289 exists.","fix":"No fix has been published for CVE-2025-52289 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52289 is a high-severity vulnerability in n/a, published on 31 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-52289 and fix it if it is affected.\n\nWhat it is: CVE-2025-52289 is a high-severity vulnerability in n/a, published on 31 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52289 exists.\n\nAffected product: n/a. 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-52289/ (Markdown: https://insights.sbomify.com/CVE-2025-52289/index.md)","id":"CVE-2025-52289","markdown":"https://insights.sbomify.com/CVE-2025-52289/index.md","name":"CVE-2025-52289","record":{"aliases":["GHSA-jgfv-5w6w-r347"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"VoIP billing software","requires_auth":"low_privilege","summary":"Newly registered users can escalate privileges to active status by manipulating a request, bypassing administrator approval in MagnusBilling.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"magnusbilling","vendor":"magnussolution"}],"cvss":{"score":8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"A Broken Access Control vulnerability in MagnusBilling v7.8.5.3 allows newly registered users to gain escalated privileges by sending a crafted request to /mbilling/index.php/user/save to set their account status fom \"pending\" to \"active\" without requiring administrator approval.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-07-31","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-31T15:50:45Z","kind":"github_poc","ref":"https://github.com/Madhav-Bhardwaj/CVE-2025-52289","stars":1,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"Privilege escalation in n/a","id":"CVE-2025-52289","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-52290"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-52288"},"products":["n/a"],"published":"2025-07-31","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-30258","kev_date_added":null,"published":"2023-06-23"},{"cvss_score":8.2,"headline":"MagnusBilling Stored Cross-Site Scripting in Login Logs","id":"CVE-2025-2609","kev_date_added":null,"published":"2025-03-21"},{"cvss_score":7.6,"headline":"MagnusBilling Stored Cross-Site Scripting in Alarm Module","id":"CVE-2025-2610","kev_date_added":null,"published":"2025-03-21"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-31","vendors":["n/a"]},"summary":"Newly registered users can escalate privileges to active status by manipulating a request, bypassing administrator approval in MagnusBilling.","url":"https://insights.sbomify.com/CVE-2025-52289/"}