dbcve.org
ApexApplication · Oracle

CVE-2026-21931

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Oracle APEX Sample Applications product of Oracle APEX (component: Brookstrut Sample App). Supported versions that are affected are 23.2.0, 23.2.1, 24.1.0, 24.2.0 and 24.2.1. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle APEX Sample Applications. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle APEX Sample Applications, 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 APEX Sample Applications accessible data as well as unauthorized read access to a subset of Oracle APEX Sample Applications 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 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 confidence

Vulnerability in Oracle APEX Sample Applications (Brookstrut Sample App) allows low-privileged attackers with network access to perform unauthorized read, insert, update, and delete operations on application data. The attack requires user interaction and despite being in a sample application, can impact additional products due to scope change.

MitigationApply Oracle patches when released for affected versions (23.2.0-24.2.1). As an interim measure, disable or remove the Brookstrut Sample App from production instances if not required.

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
ApexApplication
Affected:= 23.2.0= 23.2.1= 24.1.0= 24.2.1

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
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? 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Oracle APEX version
    Query the APEX version by running: SELECT apex_version FROM apex_release; or check the About Oracle Application Express page in the APEX administration interface.
    Affected if The version matches 23.2.0, 23.2.1, 24.1.0, or 24.2.1 exactly.
  2. Locate the Brookstrut Sample App
    Query APEX application metadata: SELECT application_id, application_name, workspace FROM apex_applications WHERE application_name LIKE '%Brookstrut%' OR application_name LIKE '%Brookstrt%';
    Affected if A row is returned indicating the Brookstrut Sample App is installed in the workspace.
  3. Verify the application is accessible
    Check if the application is published and not in restricted status: SELECT application_id, application_name, build_status, status FROM apex_applications WHERE application_name LIKE '%Brookstrut%';
    Affected if BUILD_STATUS is 'Available' or STATUS is 'Available' indicating the app is accessible to users.
  4. Confirm application is exposed to network
    Review the application security settings and any web server exposure: Check the application's Authentication Scheme setting in APEX App Builder under Security, and verify theORDS or Embedded Gateway configuration if APEX is accessible over HTTP/HTTPS.
    Affected if The application is accessible via HTTP/HTTPS network access (not localhost-only or VPN-restricted).

You are affected if your Oracle APEX version is exactly 23.2.0, 23.2.1, 24.1.0, or 24.2.1 AND the Brookstrut Sample App is installed and accessible to network users.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle patches when released for affected versions (23.2.0-24.2.1). As an interim measure, disable or remove the Brookstrut Sample App from production instances if not required.

Recommended fix Moderate confidence

Oracle APEX 24.2.2 or later (any stable release above 24.2.1)

  1. 1. Back up the current Oracle APEX installation and database before making any changes.
  2. 2. Download Oracle APEX version 24.2.2 or later from the Oracle APEX Downloads page (www.oracle.com/tools/apex/downloads).
  3. 3. Follow Oracle's documented upgrade procedure for Oracle APEX, which typically involves: a) Installing the new APEX archive, b) Running the apexins.sql script with appropriate parameters, c) Validating the installation.
  4. 4. After upgrade, verify that the Brookstrut Sample App component is functioning correctly.
  5. 5. Test that the vulnerability is no longer present by reviewing access controls in the Sample Applications.
Caveat Oracle APEX upgrades may require testing of custom applications for compatibility; review Oracle APEX upgrade documentation for any special considerations

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

Fix this in Apex Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21931 — 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 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-2026-21931 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