CVE-2025-21489
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 Advanced Outbound Telephony product of Oracle E-Business Suite (component: Region Mapping). Supported versions that are affected are 12.2.3-12.2.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Advanced Outbound Telephony, 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 Oracle Advanced Outbound Telephony accessible data as well as unauthorized read access to a subset of Oracle Advanced Outbound Telephony 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 · high confidenceInjection vulnerability in the Region Mapping component of Oracle Advanced Outbound Telephony (E-Business Suite 12.2.3-12.2.10). Unauthenticated attackers with network access via HTTP can achieve unauthorized read and modify access to some data. Requires human interaction from a victim user to exploit.
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.10CVSS 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 Oracle E-Business Suite installationCheck for Oracle E-Business Suite installation by looking for Oracle application directory structures, Oracle HTTP Server, or Oracle WebLogic Server configurations typically found in $ORACLE_HOME/applications/fnd/12.2.3 or similar paths. Query the database for FND_PRODUCT_INSTALLATIONS table or use Oracle Application Manager to confirm installation.Affected if Oracle E-Business Suite is installed and running
-
Determine E-Business Suite versionQuery the database using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the $ORACLE_HOME/appl/top/12.0.0/ sql/uatgxml.sql version header. The version is also visible in Oracle Application Manager under Site Map -> Application -> Technology Stack.Affected if Version is 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.2.8, 12.2.9, or 12.2.10
-
Check if Advanced Outbound Telephony is enabledQuery the database for installed modules: SELECT application_id, application_name FROM fnd_application_vl WHERE application_name LIKE '%Advanced%Outbound%'; or check Oracle Application Manager for enabled product installations related to Telephony.Affected if Advanced Outbound Telephony product/installation is found and enabled in the E-Business Suite instance
-
Verify Region Mapping component accessibilityCheck Oracle Application Manager or the E-Business Suite profile options for Region Mapping module configuration. Look for URL endpoints under /oa_region_mapping or similar paths in Oracle HTTP Server configuration files (httpd.conf or oracle_apache.conf).Affected if Region Mapping component is configured and accessible through web interfaces
-
Assess HTTP network exposureReview Oracle HTTP Server or Oracle WebLogic Server listener configurations to determine if E-Business Suite pages are exposed to network-accessible HTTP/HTTPS endpoints. Check firewall rules and load balancer configurations for exposure.Affected if Region Mapping component is accessible via HTTP/HTTPS from network addresses
The environment is affected if Oracle E-Business Suite versions 12.2.3 through 12.2.10 are running with the Advanced Outbound Telephony and Region Mapping component enabled and exposed to HTTP network access, since unauthenticated attackers can exploit this vulnerability with victim user interaction.
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.
From vendor dataApply Oracle's latest security patches for the affected E-Business Suite versions. Implement network segmentation and monitor for suspicious interactions given the user-interaction requirement.
- 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-21489 — 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-21489 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