IprocurementApplication · Oracle

CVE-2023-21973

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-18

Fix available

A fix is available. Upgrade to after 12.2.12 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

Vulnerability in the Oracle iProcurement product of Oracle E-Business Suite (component: E-Content Manager Catalog). Supported versions that are affected are 12.2.3-12.2.12. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle iProcurement. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle iProcurement, 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 iProcurement accessible data as well as unauthorized read access to a subset of Oracle iProcurement 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

Injection vulnerability in the E-Content Manager Catalog component of Oracle iProcurement (versions 12.2.3-12.2.12) allowing low-privileged attackers with network access via HTTP to perform unauthorized read, insert, update, and delete operations on a subset of iProcurement data. Human interaction is required for exploitation.

MitigationApply Oracle Critical Patch Update (CPU) April 2023 or later. Until patched, implement compensating controls such as web application firewall rules and strict input validation on iProcurement endpoints.

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

IprocurementApplication

Affected:>= 12.2.3, <= 12.2.12

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.

Confirm Oracle iProcurement is installed

Query the Oracle Applications tables (e.g., select release_name from fnd_product_groups where product_code like '%POX%' or product_code = 'ICX') or check the iProcurement login page for version information

Affected if iProcurement is present in the environment
Identify installed iProcurement version

Run SQL query: SELECT release_name FROM fnd_product_groups WHERE product_code = 'POX' or check the Oracle Applications About page for iProcurement patch level

Affected if Version is between 12.2.3 and 12.2.12 inclusive
Verify E-Content Manager Catalog component is configured

Check Oracle Application Manager (OAM) or query fnd_profile_options for E-Content Manager related profiles (such as 'ECX: Content Manager Integration Enabled')

Affected if E-Content Manager Catalog module is enabled or configured in the iProcurement instance
Confirm network accessibility via HTTP

Verify if iProcurement web endpoints (typically /OA_HTML/icxpnameroute, /OA_HTML/por, or /OA_JAVA/oracle/apps/icx/por/) are exposed to network and reachable without VPN or multi-factor authentication

Affected if iProcurement is accessible over HTTP/HTTPS from untrusted networks without strong authentication controls
Review audit and access logs for suspicious E-Content Manager queries

Examine Oracle HTTP Server access logs and Oracle Database audit trails for anomalous SQL patterns or unusual data access patterns targeting the E-Content Manager Catalog tables

Affected if Unusual or unauthorized queries appear in logs related to iProcurement catalog functions

The environment is affected if Oracle iProcurement version 12.2.3 through 12.2.12 is installed with E-Content Manager Catalog enabled and accessible over the network.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.12

Interim mitigation

Apply Oracle Critical Patch Update (CPU) April 2023 or later. Until patched, implement compensating controls such as web application firewall rules and strict input validation on iProcurement endpoints.

Recommended fix High confidence

Oracle E-Business Suite 12.2.13 or later (includes fix) or April 2023 CPU

1. Identify the current Oracle E-Business Suite 12.2.x patch level by navigating to the Oracle Applications Manager and checking the version information.
2. Apply the April 2023 Critical Patch Update (CPU) which includes the fix for CVE-2023-21973 in the Oracle iProcurement E-Content Manager Catalog component.
3. Alternatively, if available, apply the specific one-off patch for CVE-2023-21973 for Oracle E-Business Suite 12.2.
4. After applying the patch, verify the fix by confirming the patch is installed in Oracle Applications Manager and testing iProcurement functionality.
5. Restart affected Oracle WebLogic and Oracle HTTP Server services as required by the patch installation.
6. Validate that the vulnerability is resolved by reviewing the Oracle Metalink patch documentation for the applied fix.

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

Fix this in Iprocurement Scoped from the published advisory

Consultation6.0 h
Implementation12.0 h
Testing20.0 h
Review / QA6.0 h

44.0 hours of engineering $7,440

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2023-21973 — 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-2023-21973 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-21973?

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 after 12.2.12 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Iprocurement

Remediation

Need this fixed?

Fix this in Iprocurement 44 hrs · Moderate

Typical engagement from $7,440

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2023-21973 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