Jd Edwards Enterpriseone ToolsApplication · Oracle

CVE-2025-21507

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-21

Fix available

A fix is available. Upgrade to 9.2.9.0 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

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 low privileged 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 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

Technical summary

dbcve analysis · moderate confidence

Vulnerability in JD Edwards EnterpriseOne Tools Web Runtime SEC component allows low-privileged attackers with network access via HTTP to compromise the system. Requires human interaction and results in unauthorized read, insert, update, and delete access to a subset of accessible data. The scope change indicates the vulnerability may impact additional products beyond the primary target.

MitigationApply Oracle JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. Review and harden Web Runtime SEC configurations while awaiting the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Jd Edwards Enterpriseone ToolsApplication

Affected:< 9.2.9.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify JD Edwards EnterpriseOne Tools is installed

Check for the JD Edwards installation directory (typically $JDEDWARDS_HOME or similar) and look for Tools components. On Windows, check Program Files/Oracle. On Unix/Linux, check /opt/oracle or /u01/oracle. Look for 'Tools' folder or 'jdeenv.sh' scripts.

Affected if The JD Edwards EnterpriseOne Tools software is present on the system
Identify the installed Tools version

Locate the version file or check through the JD Edwards Administration Console. Common locations: <install_dir>/Tools/VERSIONS.txt, or run 'jde -version' from the command line, or check the JDE.INI / jde.ini configuration file for 'ToolsRelease' or 'Version' entries.

Affected if The installed version is lower than 9.2.9.0 (for example, 9.2.8.x, 9.2.7.x, etc.)
Confirm Web Runtime component is enabled

Check the JD Edwards EnterpriseOne HTML/Web Server configuration. Look for Web Runtime settings in the jde.ini file under sections like [HTML SERVER] or [WORLD WIDE WEB], or check the Apache/Oracle HTTP Server configuration that serves JD Edwards web applications.

Affected if The Web Runtime (HTML Server or World Wide Web) is configured and running, exposing HTTP interfaces
Check network accessibility of Web Runtime

Review firewall rules and web server bindings. Determine if the JD Edwards Web Runtime ports (commonly 80, 443, or custom ports like 8080, 8443) are exposed to network access rather than localhost only. Check httpd.conf or Oracle HTTP Server config for Listen directives.

Affected if The Web Runtime SEC component is reachable over the network via HTTP/HTTPS from untrusted networks

User is affected if JD Edwards EnterpriseOne Tools version is below 9.2.9.0 AND the Web Runtime SEC component is enabled and network-accessible via HTTP.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 9.2.9.0 or later

Fixed in 9.2.9.0

Interim mitigation

Apply Oracle JD Edwards EnterpriseOne Tools version 9.2.9.0 or later. Review and harden Web Runtime SEC configurations while awaiting the patch.

Recommended fix High confidence

Upgrade to JD Edwards EnterpriseOne Tools version 9.2.9.0 or later

1. Identify the current version of JD Edwards EnterpriseOne Tools deployed in your environment using the Oracle JD Edwards Deployment Server or Enterprise Manager
2. Confirm the installed version is below 9.2.9.0, as versions prior to 9.2.9.0 are affected by this CSRF vulnerability
3. Obtain JD Edwards EnterpriseOne Tools 9.2.9.0 or later from Oracle's official distribution channels (My Oracle Support or Oracle Software Delivery Cloud)
4. Create a comprehensive backup of the current JD Edwards EnterpriseOne Tools environment, including the database and configuration files
5. Set up a non-production (staging or test) environment that mirrors production to validate the upgrade process
6. Execute the upgrade to version 9.2.9.0 or later in the non-production environment first
7. Verify that the Web Runtime SEC component is functioning correctly and that CSRF protections are in place after the upgrade
8. Schedule a maintenance window and apply the upgrade to the production environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jd Edwards Enterpriseone Tools Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA4.0 h

22.0 hours of engineering $3,860

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-21507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21507 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-21507?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to 9.2.9.0 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Jd Edwards Enterpriseone Tools

Remediation

Need this fixed?

Fix this in Jd Edwards Enterpriseone Tools 22 hrs · Moderate

Typical engagement from $3,860

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-21507 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References