CVE-2025-21538
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.2. 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 confidenceUnauthenticated remote vulnerability in JD Edwards EnterpriseOne Tools Web Runtime SEC component allows attackers via HTTP to read, insert, update, or delete accessible data. Exploitation requires human interaction (e.g., tricking a user into clicking a malicious link), and the vulnerability's scope change allows impact to additional products beyond the primary target.
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.2CVSS 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 JD Edwards EnterpriseOne Tools installationLocate the JD Edwards EnterpriseOne Tools installation directory and identify the installed version number, typically found in version manifest files, about dialogs, or installation logs within the Tools directory structureAffected if Installation is present and version cannot be confirmed to be 9.2.9.2 or later
-
Confirm installed version against affected rangeCompare your installed JD Edwards EnterpriseOne Tools version to the affected range: any version prior to 9.2.9.2 is vulnerableAffected if Installed version is lower than 9.2.9.2
-
Determine if Web Runtime SEC component is enabledCheck the JD Edwards EnterpriseOne Tools configuration or deployment settings to verify whether the Web Runtime SEC (Security) component is enabled and deployed on the systemAffected if Web Runtime SEC component is enabled and deployed
-
Check HTTP exposure of Web RuntimeInspect web server or enterprise server configuration to determine if HTTP endpoints for the Web Runtime are exposed externally or accessible over the network without authentication barriersAffected if HTTP access to Web Runtime SEC endpoint is externally accessible
-
Review HTTP access logs for suspicious requestsExamine web server access logs and HTTP traffic logs for requests targeting the Web Runtime SEC endpoint, looking for unusual or malicious query patternsAffected if Logs show suspicious or malicious HTTP requests to Web Runtime SEC endpoints
The environment is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.2 AND the Web Runtime SEC component is enabled and accessible via HTTP.
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.2
Upgrade to JD Edwards EnterpriseOne Tools version 9.2.9.2 or later to remediate this vulnerability. Implement web application firewall rules as an interim control to block malicious HTTP requests targeting the Web Runtime SEC endpoint.
9.2.9.2 or later
- Upgrade JD Edwards EnterpriseOne Tools to version 9.2.9.2 or later
- After upgrading, verify the Web Runtime SEC component is updated to the patched version
- Test that CSRF protections are functioning correctly in the Web Runtime
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21538 — 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-21538 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