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

> Attackers can inject malicious scripts into category names, leading to XSS execution in victims' browsers when viewing associated documents.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-hcjx-v7fg-j456

## What is CVE-2025-25461?

CVE-2025-25461 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Stored Cross-Site Scripting (XSS) vulnerability exists in SeedDMS 6.0.29. A user or rogue admin with the "Add Category" permission can inject a malicious XSS payload into the category name field. When a document is subsequently associated with this category, the payload is stored on the server and rendered without proper sanitization or output encoding. This results in the XSS payload executing in the browser of any user who views the document.

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

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

It affects 1 product.


Products: Seeddms Seeddms.

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

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

## Is CVE-2025-25461 being exploited?

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

Public exploit code:

- SeedDMS Stored Cross Site Scripting(XSS) (github_poc): https://github.com/RoNiXxCybSeC0101/CVE-2025-25461

## Other vulnerabilities in n/a

- [CVE-2022-44938](https://insights.sbomify.com/CVE-2022-44938/): Weak cryptography in n/a (critical 9.8)
- [CVE-2021-33223](https://insights.sbomify.com/CVE-2021-33223/): Privilege escalation in n/a (high 8.8)
- [CVE-2018-12940](https://insights.sbomify.com/CVE-2018-12940/): File upload in n/a (high 8.8)
- [CVE-2018-12941](https://insights.sbomify.com/CVE-2018-12941/): Command injection in n/a (high 8.8)
- [CVE-2018-12942](https://insights.sbomify.com/CVE-2018-12942/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25461 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2025. Any signed-in user can exploit it over the network, 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-25461 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-25461/ (Markdown: https://insights.sbomify.com/CVE-2025-25461/index.md)
```

## Sources

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

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