{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2610 exists.","fix":"No fix has been published for CVE-2025-2610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2610 is a high-severity cross-site scripting vulnerability in MagnusSolution MagnusBilling, published on 21 Mar 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-2610 and fix it if it is affected.\n\nWhat it is: CVE-2025-2610 is a high-severity cross-site scripting vulnerability in MagnusSolution MagnusBilling, published on 21 Mar 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-2610 exists.\n\nAffected product: MagnusSolution MagnusBilling. 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-2610/ (Markdown: https://insights.sbomify.com/CVE-2025-2610/index.md)","id":"CVE-2025-2610","markdown":"https://insights.sbomify.com/CVE-2025-2610/index.md","name":"CVE-2025-2610","record":{"aliases":["GHSA-5fww-m73j-6p23"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Billing software","requires_auth":"low_privilege","summary":"Authenticated attackers can inject malicious scripts into the Alarm Module, potentially compromising user sessions or executing code.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"magnusbilling","vendor":"magnussolution"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Improper neutralization of input during web page generation vulnerability in MagnusSolution MagnusBilling (Alarm Module modules) allows authenticated stored cross-site scripting. This vulnerability is associated with program files protected/components/MagnusLog.Php.\n\nThis issue affects MagnusBilling: through 7.3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-2610.yaml","stars":null,"title":"MagnusBilling Alarm Module - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":false,"headline":"MagnusBilling Stored Cross-Site Scripting in Alarm Module","id":"CVE-2025-2610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"ICTBroadcast \u003c= 7.4 Unauthenticated Session Cookie RCE","id":"CVE-2025-2611"},"packages":[],"prev":{"headline":"MagnusBilling Stored Cross-Site Scripting in Login Logs","id":"CVE-2025-2609"},"products":["MagnusBilling"],"published":"2025-03-21","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":8,"headline":"Privilege escalation in n/a","id":"CVE-2025-52289","kev_date_added":null,"published":"2025-07-31"}],"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":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["MagnusSolution"]},"summary":"Authenticated attackers can inject malicious scripts into the Alarm Module, potentially compromising user sessions or executing code.","url":"https://insights.sbomify.com/CVE-2025-2610/"}