Application ExpressApplication · Oracle

CVE-2023-21983

MEDIUM · 5.6 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to after 22.2 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Vulnerability in the Application Express Administration product of Oracle Application Express (component: None). Supported versions that are affected are Application Express Administration: 18.2-22.2. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Application Express Administration. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Application Express Administration accessible data as well as unauthorized read access to a subset of Application Express Administration accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Application Express Administration. CVSS 3.1 Base Score 5.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L).

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

A detailed technical summary for this CVE is being prepared.

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
Application ExpressApplication
Affected:>= 18.2, <= 22.2

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.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 · scoped
Upgrade available Upgrade to a release after 22.2
Vendor patch www.oracle.com →
Recommended fix High confidence

Oracle Application Express 23.1 or later (any version beyond 22.2)

  1. 1. Review the Oracle Critical Patch Update advisory for July 2023 at https://www.oracle.com/security-alerts/cpujul2023.html to confirm the specific patch requirements for CVE-2023-21983
  2. 2. Identify the current Oracle Application Express version in use by querying the apex_version view or checking the About Application Express page in the administration console
  3. 3. Download and install Oracle Application Express 23.1 or later from the Oracle APEX download page (https://www.oracle.com/tools/apex/downloads.html) as this version is beyond the affected 22.2 range
  4. 4. Before upgrading, back up the existing APEX installation including the APEX schema and any custom configurations
  5. 5. Follow the Oracle APEX upgrade instructions in the Installation Guide to upgrade from the current version to 23.1 or later
  6. 6. After upgrade, verify the Application Express Administration console is accessible and functioning correctly
  7. 7. Confirm the vulnerability is addressed by reviewing the release notes for the new version which should include CVE-2023-21983 in the security fixes
Caveat Review Oracle APEX 23.x release notes for any deprecated features or migration considerations; some APEX utilities or APIs may have changed behavior

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-21983 — 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 sources

Practitioner notes

Contributed

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

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