CVE-2025-21513
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an access control vulnerability in JD Edwards EnterpriseOne Tools Web Runtime SEC component. An unauthenticated attacker with network access via HTTP can achieve unauthorized read, insert, update, and delete access to a subset of the application's data. The requirement for human interaction suggests the attack may involve social engineering or tricking a legitimate user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.2.9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed JD Edwards EnterpriseOne Tools versionCheck the version of Oracle JD Edwards EnterpriseOne Tools installed in your environment. This is typically found in the installation directory, Oracle Enterprise Manager, or via the JD Edwards Deployment Server. Common paths include the 'SystemXX' directory or check the 'release' information in the JDE Plan table.Affected if The installed version is lower than 9.2.9.0 (for example, 9.2.8.x, 9.2.7.x, or earlier releases)
-
Verify Web Runtime SEC component is configuredCheck if the JD Edwards Web Runtime (HTML/World) server components are installed and running. Look for the 'SEC' (Security) component in the Web Runtime configuration. Inspect the web server configuration files such as 'jde.ini' or 'jas.ini' for SEC-related settings and confirm the Web Runtime service is active.Affected if The Web Runtime SEC component is installed and running, exposing the vulnerability surface
-
Confirm HTTP exposure of Web RuntimeExamine your network configuration to determine if the JD Edwards Web Runtime HTTP listeners are accessible from the network. Check web server configuration (IIS, Oracle HTTP Server, or Apache) bindings and firewall rules to see if port 80/443 or custom Web Runtime ports are exposed externally or to untrusted networks.Affected if HTTP/HTTPS ports for Web Runtime are reachable from untrusted networks or the internet
-
Review access control configurationsInspect the SEC component's access control settings in the JD Edwards security configuration. Check if the Web Runtime SEC component has proper role-based access controls configured and verify whether anonymous or unauthenticated access paths exist through the web interface.Affected if Unauthenticated access paths through the Web Runtime are allowed or misconfigured
You are affected if your installed JD Edwards EnterpriseOne Tools version is below 9.2.9.0 AND the Web Runtime SEC component is enabled and accessible via HTTP, allowing unauthenticated network attackers to potentially manipulate application data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2.9.0
Oracle has released version 9.2.9.0 which addresses this vulnerability. Organizations should upgrade to this version or later. Network segmentation and WAF rules may provide interim mitigation to limit HTTP exposure.
9.2.9.0 or later
- 1. Identify the current version of JD Edwards EnterpriseOne Tools installed in your environment
- 2. Review the Oracle Critical Patch Update advisory for January 2025 to obtain the specific patch identifier for CVE-2025-21513
- 3. Download the required patch or upgrade package from Oracle Support
- 4. Test the upgrade in a non-production environment to verify compatibility with existing customizations
- 5. Create a full backup of the current environment before applying the upgrade
- 6. Apply the upgrade to version 9.2.9.0 or later following Oracle's standard upgrade procedures
- 7. Verify the patch was applied successfully and the Web Runtime SEC component is updated
- 8. Test critical business workflows to ensure functionality is intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-21513 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data