# CVE-2025-21513: Cross-site request forgery in JD Edwards EnterpriseOne Tools

> Unauthenticated attackers can perform unauthorized data modifications and reads via CSRF attacks requiring user interaction in JD Edwards EnterpriseOne.

- **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:** 21 Jan 2025
- **Updated:** 23 Jan 2025
- **Also known as:** GHSA-rm9r-5rv8-5jw4

## What is CVE-2025-21513?

CVE-2025-21513 is a medium-severity vulnerability in Oracle Jd Edwards Enterpriseone Tools, published on 21 Jan 2025. 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

Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Web Runtime SEC).  Supported versions that are affected are Prior to 9.2.9.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in JD Edwards EnterpriseOne Tools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of JD Edwards EnterpriseOne Tools accessible data as well as  unauthorized read access to a subset of JD Edwards EnterpriseOne Tools accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

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

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

It affects 1 product.


Products: Oracle Jd Edwards Enterpriseone Tools.

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

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

## Is CVE-2025-21513 being exploited?

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

## Other vulnerabilities in Oracle Jd Edwards Enterpriseone Tools

- [CVE-2026-60627](https://insights.sbomify.com/CVE-2026-60627/): Auth bypass in JD Edwards EnterpriseOne Tools (critical 9.9)
- [CVE-2026-61272](https://insights.sbomify.com/CVE-2026-61272/): Auth bypass in JD Edwards EnterpriseOne Tools (critical 9.8)
- [CVE-2026-46878](https://insights.sbomify.com/CVE-2026-46878/): Auth bypass in JD Edwards EnterpriseOne Tools (critical 9.8)
- [CVE-2026-46879](https://insights.sbomify.com/CVE-2026-46879/): Auth bypass in JD Edwards EnterpriseOne Tools (critical 9.8)
- [CVE-2026-46880](https://insights.sbomify.com/CVE-2026-46880/): Auth bypass in JD Edwards EnterpriseOne Tools (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-21513 is a medium-severity vulnerability in Oracle Jd Edwards Enterpriseone Tools, published on 21 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-21513 in the wild and no public exploit code.

Affected product: Oracle Jd Edwards Enterpriseone Tools. 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-21513/ (Markdown: https://insights.sbomify.com/CVE-2025-21513/index.md)
```

## Sources

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

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