CVE-2026-21972
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 Configurator product of Oracle E-Business Suite (component: User Interface). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Configurator. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Configurator accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 confidenceOracle Configurator User Interface component in Oracle E-Business Suite versions 12.2.3-12.2.15 contains an information disclosure vulnerability exploitable via unauthenticated HTTP requests, allowing attackers to read a subset of accessible data.
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.15CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 E-Business Suite installation directory (typically $ORACLE_HOME) and verify the presence of Oracle Applications. Check for the presence of the Configurator component directory under $ORACLE_HOME/forms/java or $ORACLE_HOME/oc4j.Affected if Oracle E-Business Suite with Configurator component is not installed or not in use.
-
Determine Oracle Configurator versionUse the Oracle Application Manager (OAM) or run the command 'adident Header $ORACLE_HOME/forms/java/oracle/apps/fnd/czui/ConfiguratorMain.class' if available. Alternatively, query the FND_PRODUCT_INSTALLATIONS table via SQL if database access is available: SELECT product_version FROM fnd_product_installations WHERE product_name LIKE '%Configurator%';Affected if The installed version falls within 12.2.3 through 12.2.15.
-
Verify Configurator UI HTTP accessibilityCheck if the Configurator UI servlet is exposed by accessing the URL pattern typically used (such as /servlets/Configurator or /OA_HTML/Configurator) via an unauthenticated HTTP request to the E-Business Suite web server. Review the Oracle HTTP Server configuration files (httpd.conf or oracle_apache.conf) for any RewriteRules or Alias directives exposing the Configurator paths.Affected if The Configurator UI endpoint is reachable via HTTP/HTTPS without authentication.
-
Review web entry point securityExamine the Oracle E-Business Suite function security configuration for the Configurator functions. Query SELECT function_name, web_html_name FROM fnd_form_functions WHERE web_html_name LIKE '%configurator%' OR function_name LIKE '%configurator%'; to identify protected functions. Check if guest user access or public shortcuts are enabled for these functions.Affected if The Configurator functions are accessible to unauthenticated or low-privileged users.
The environment is affected if Oracle E-Business Suite 12.2.3-12.2.15 with the Configurator component is installed and the Configurator UI is accessible via unauthenticated HTTP requests.
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 relevant Oracle Critical Patch Update (CPU) for CVE-2026-21972 to the Oracle Configurator component, or apply the specific patch for this vulnerability from Oracle Support.
Oracle Configurator 12.2.16 or later (next available release after 12.2.15)
- 1. Identify current Oracle Configurator version by navigating to Oracle Application Manager > Oracle Configurator or checking the about page.
- 2. Confirm the version falls within the affected range (12.2.3-12.2.15).
- 3. Subscribe to Oracle Critical Patch Updates to receive future security patches: https://www.oracle.com/security-alerts/
- 4. Apply the latest Oracle E-Business Suite Fusion Middleware plug-in updates for Configurator.
- 5. After upgrade, verify the Configurator UI is accessible and functioning normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21972 — 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-2026-21972 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