CVE-2025-21506
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 Oracle Project Foundation product of Oracle E-Business Suite (component: Technology Foundation). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Project Foundation. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Project Foundation accessible data as well as unauthorized access to critical data or complete access to all Oracle Project Foundation accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 confidenceHTTP-based vulnerability in Oracle Project Foundation (Technology Foundation component) affecting EBS versions 12.2.3-12.2.13. Allows low-privileged attackers with network access to create, delete, or modify critical data, or gain unauthorized read access to sensitive information.
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>= 12.2.3, <= 12.2.13CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm Oracle E-Business Suite installationLocate the EBS application directory structure (typically under $APPL_TOP) or run Oracle-adopted version commands such as 'adident' against executables in the EBS bin directoryAffected if Oracle E-Business Suite is not present - not affected
-
Determine installed Oracle EBS versionExecute the Oracle EBS version query using SQL against the APPS schema: SELECT release_name FROM fnd_product_groups; or check the OAM (Oracle Application Manager) diagnostics page showing the version numberAffected if Version falls between 12.2.3 and 12.2.13 inclusive - in the affected range
-
Verify Project Foundation module is enabledQuery the fnd_product_installations table in the APPS schema for the PA (Project Foundation) product installation status, or inspect installed modules via Oracle Application ManagerAffected if Project Foundation module shows as Installed or Enabled - vulnerable component is present
-
Determine network accessibility of EBS HTTP interfacesReview network configuration files, firewall rules, and web server (Apache/Oracle HTTP Server) listener settings to check which IP addresses and networks can reach the EBS login pages and web servicesAffected if HTTP ports (typically 8000-8009) are reachable from untrusted or public networks - attack surface is exposed
User is affected if Oracle EBS version 12.2.3-12.2.13 is installed with Project Foundation enabled and HTTP interfaces are accessible to untrusted network attackers
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 the latest Oracle Critical Patch Update for Oracle E-Business Suite. Restrict network access to Oracle EBS HTTP interfaces to trusted networks only, and audit existing user privileges.
- Check Oracle Support for the latest Critical Patch Update (CPU) that addresses CVE-2025-21506
- Apply the relevant security patch for Oracle E-Business Suite 12.2.x via Oracle Support
- Verify the patch was applied successfully by checking the applied patches in Oracle Application Manager
- Test the Oracle Project Foundation component to confirm the authorization fix is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21506 — 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-21506 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