CVE-2025-53060
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 9.2.0.0-9.2.9.4. 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 HTTP attacks against the Web Runtime SEC component of JD Edwards EnterpriseOne Tools allow attackers to partially read and modify data without credentials. The vulnerability requires human interaction (likely for session hijacking or social engineering), operates over the network with low complexity, and can impact additional products beyond the core Tools product due to scope change.
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.0.0, <= 9.2.9.4CVSS 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 Tools versionLocate the JD Edwards EnterpriseOne Tools installation directory and check the version information, typically found in installation logs, the server configuration, or the 'Server Manager' interface. Common locations include the 'SYSTABLE' database or the 'jde.ini' configuration file.Affected if The installed version falls within the range >= 9.2.0.0 and <= 9.2.9.4
-
Verify Web Runtime SEC component statusCheck if the Web Runtime SEC (Security) component is installed and enabled on the JD Edwards application server. This can be verified through the EnterpriseOne Server Manager console or by reviewing the deployed web application configurations in the application server (such as Oracle WebLogic or IBM WebSphere).Affected if Web Runtime SEC component is installed and actively running on the affected Tools version
-
Assess network exposure of Web Runtime interfacesDetermine if Web Runtime HTTP endpoints are exposed to untrusted networks. Review firewall rules, load balancer configurations, and web server access controls that govern external access to the JD Edwards Web Runtime port (commonly port 80/443 or custom ports configured during installation).Affected if Web Runtime interfaces are accessible from untrusted or public network segments without proper access restrictions
-
Review HTTP access logs for suspicious patternsExamine web server and Web Runtime access logs for anomalous HTTP requests that may indicate exploitation attempts, such as unusual request parameters, repeated authentication bypass patterns, or unexpected data access patterns.Affected if Logs reveal suspicious or anomalous HTTP requests targeting Web Runtime endpoints, especially from untrusted sources
A user is affected if JD Edwards EnterpriseOne Tools version is between 9.2.0.0 and 9.2.9.4 inclusive AND the Web Runtime SEC component is enabled and exposed to network access.
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 · scopedApply Oracle's latest security patches for JD Edwards EnterpriseOne Tools (version 9.2.9.5 or later). Until patched, restrict network access to Web Runtime interfaces and monitor for suspicious HTTP requests.
- Check Oracle's Critical Patch Updates (CPU) for October 2025 or subsequent updates for the JD Edwards EnterpriseOne Tools security patch addressing CVE-2025-53060
- Apply the Oracle-provided security patch for the Web Runtime SEC component
- After patching, verify the fix by reviewing access controls in the Web Runtime configuration
- Test that the unauthorized access vectors are now properly restricted
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-53060 — 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-53060 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