{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70128 exists.","fix":"No fix has been published for CVE-2025-70128 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70128 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-70128 and fix it if it is affected.\n\nWhat it is: CVE-2025-70128 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, 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-70128 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-70128/ (Markdown: https://insights.sbomify.com/CVE-2025-70128/index.md)","id":"CVE-2025-70128","markdown":"https://insights.sbomify.com/CVE-2025-70128/index.md","name":"CVE-2025-70128","record":{"aliases":["GHSA-35vp-x4m3-rrq9","UBUNTU-CVE-2025-70128"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PluXml CMS","requires_auth":"none","summary":"Attackers can inject JavaScript into comment links, executing code in the admin panel to compromise administrator accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pluxml","vendor":"pluxml"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A Stored Cross-Site Scripting (XSS) vulnerability exists in the PluXml article comments feature for PluXml versions 5.8.22 and earlier. The application fails to properly sanitize or validate user-supplied input in the \"link\" field of a comment. An attacker can inject arbitrary JavaScript code using a \u003cscript\u003e element. The injected payload is stored in the database and subsequently rendered in the Administration panel's \"Comments\" section when administrators review submitted comments. Importantly, the malicious script is not reflected in the public-facing comments interface, but only within the backend administration view. Alternatively, users of Administrator, Moderator, Manager roles can also directly input crafted payloads into existing comments. This makes the vulnerability a persistent XSS issue targeting administrative users. This affects /core/admin/comments.php, while CVE-2022-24585 affects /core/admin/comment.php, a uniquely distinct vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-70128","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2025-70129"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-70123"},"products":["n/a"],"published":"2026-03-10","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-18185","kev_date_added":null,"published":"2020-10-02"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2024-22636","kev_date_added":null,"published":"2024-01-25"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2022-25018","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2012-2227","kev_date_added":null,"published":"2012-08-26"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2007-3432","kev_date_added":null,"published":"2007-06-27"},{"cvss_score":6.5,"headline":"Code injection in n/a","id":"CVE-2025-67436","kev_date_added":null,"published":"2025-12-22"}],"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":"2026-03-12","vendors":["n/a"]},"summary":"Attackers can inject JavaScript into comment links, executing code in the admin panel to compromise administrator accounts.","url":"https://insights.sbomify.com/CVE-2025-70128/"}