# CVE-2025-25772: Cross-site request forgery in n/a

> Attackers can exploit CSRF in Jspxcms to arbitrarily add Administrator accounts, leading to privilege escalation and account takeover.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-r4wq-76x5-pwj9

## What is CVE-2025-25772?

CVE-2025-25772 is a medium-severity vulnerability in n/a, published on 21 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Cross-Site Request Forgery (CSRF) in the component /back/UserController.java of Jspxcms v9.0 to v9.5 allows attackers to arbitrarily add Administrator accounts via a crafted request.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Ujcms Jspxcms.

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

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

## Is CVE-2025-25772 being exploited?

There is no known exploitation of CVE-2025-25772 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-23329](https://insights.sbomify.com/CVE-2022-23329/): Code injection in n/a (critical 9.8)
- [CVE-2022-28090](https://insights.sbomify.com/CVE-2022-28090/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2024-1256](https://insights.sbomify.com/CVE-2024-1256/): Jspxcms filter_text.do cross site scripting (low 3.5)
- [CVE-2024-1257](https://insights.sbomify.com/CVE-2024-1257/): Jspxcms find_text.do cross site scripting (low 3.5)
- [CVE-2024-0599](https://insights.sbomify.com/CVE-2024-0599/): Jspxcms Document Management Page InfoController.java cross site scripting (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25772 is a medium-severity vulnerability in n/a, published on 21 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25772 in the wild and no public exploit code.

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-25772/ (Markdown: https://insights.sbomify.com/CVE-2025-25772/index.md)
```

## Sources

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

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