dbcve.org
Application ExpressApplication · Oracle

CVE-2025-50067

CRITICAL · 9.0 CVSS v3.1 Published 2025-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Oracle Application Express (component: Strategic Planner Starter App). Supported versions that are affected are 24.2.4 and 24.2.5. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Application Express. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Application Express, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Application Express. CVSS 3.1 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H).

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
How this class of weakness works · CWE-601

The application redirects the browser to a URL taken from user input without validating it, so an attacker can craft a link on your trusted domain that quietly bounces victims to a malicious site. It is a staple of phishing and token theft. The fix is to allow-list redirect destinations or use indirect reference keys, never a raw user-supplied URL.

General guidance for the open redirect class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:= 24.2.4= 24.2.5

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
High
Integrity
High
Availability
High

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

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Recommended fix Moderate confidence

Oracle Application Express 24.2.6 or later (or latest 24.2.x/24.3.x stable release)

  1. 1. Review the Oracle Critical Patch Update advisory for July 2025 at https://www.oracle.com/security-alerts/cpujul2025.html to confirm the fixed version for Oracle Application Express.
  2. 2. Identify the current Oracle Application Express version by querying SELECT version_no FROM apex_release;
  3. 3. Download and install the patched Oracle Application Express version (24.2.6 or later in the 24.2.x series, or the latest stable release) from Oracle Support.
  4. 4. After upgrading, verify the patch was applied successfully by checking the new version number.
  5. 5. Test the Strategic Planner Starter App functionality to ensure the open redirect vulnerability is remediated and the application works correctly.
  6. 6. Review and validate that no other open redirect vulnerabilities exist in custom applications using the APEX URL checker or manual code review.
Caveat Oracle APEX patch upgrades typically have minimal breaking changes, but review Oracle's upgrade notes for any deprecation notices or configuration changes required

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

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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