# CVE-2025-70128: Cross-site scripting in n/a

> Attackers can inject JavaScript into comment links, executing code in the admin panel to compromise administrator accounts.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-35vp-x4m3-rrq9, UBUNTU-CVE-2025-70128

## What is CVE-2025-70128?

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.

### Official 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 <script> 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-70128?

It affects 1 product.


Products: Pluxml Pluxml.

## How do I fix CVE-2025-70128?

No fix has been published for CVE-2025-70128 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-70128 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70128 exists.

## Other vulnerabilities in n/a

- [CVE-2020-18185](https://insights.sbomify.com/CVE-2020-18185/): Code injection in n/a (critical 9.8)
- [CVE-2024-22636](https://insights.sbomify.com/CVE-2024-22636/): Code injection in n/a (high 8.8)
- [CVE-2022-25018](https://insights.sbomify.com/CVE-2022-25018/): Code injection in n/a (high 8.8)
- [CVE-2012-2227](https://insights.sbomify.com/CVE-2012-2227/): Path traversal in n/a (high 7.5)
- [CVE-2007-3432](https://insights.sbomify.com/CVE-2007-3432/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70128 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70128 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70128/ (Markdown: https://insights.sbomify.com/CVE-2025-70128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70128
- OSV: https://osv.dev/vulnerability/CVE-2025-70128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70128/
Summaries are generated and may contain mistakes; the official description above is the record.