dbcve.org
Utilities FrameworkApplication · Oracle

CVE-2026-21924

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 Utilities Application Framework product of Oracle Utilities Applications (component: General). Supported versions that are affected are 4.4.0.3.0, 4.5.0.0.0, 4.5.0.1.1, 4.5.0.1.3, 4.5.0.2.0, 25.4 and 25.10. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Utilities Application Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Utilities Application Framework, 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 Utilities Application Framework accessible data as well as unauthorized read access to a subset of Oracle Utilities Application Framework 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

Cross-site request forgery (CSRF) vulnerability in Oracle Utilities Application Framework allows low-privileged authenticated attackers via HTTP to perform unauthorized read, insert, update, and delete operations on accessible data. Exploitation requires human interaction (victim clicking a link), and the scope extends beyond the vulnerable component to impact additional products.

MitigationApply Oracle Critical Patch Updates for Oracle Utilities Applications. Implement anti-CSRF tokens on state-changing operations and validate origin/Referer headers. Consider implementing SameSite cookie attributes.

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
Utilities FrameworkApplication
Affected:= 4.3.0.3.0= 4.5.0.0.0= 4.5.0.1.1= 4.5.0.1.3= 4.5.0.2.0= 25.4= 25.10

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 Oracle Utilities Application Framework version
    Locate the installed version of Oracle Utilities Application Framework by checking the application's version file, about page, or administration console. Common locations include the system information page or version.properties file in the application deployment directory.
    Affected if The installed version matches exactly 4.3.0.3.0, 4.5.0.0.0, 4.5.0.1.1, 4.5.0.1.3, 4.5.0.2.0, 25.4, or 25.10
  2. Verify CSRF token implementation on state-changing operations
    Inspect the application's form submissions and API endpoints that perform insert, update, or delete operations. Examine the HTML source or API responses to determine whether a unique anti-CSRF token is required and validated for each state-changing request.
    Affected if State-changing operations lack anti-CSRF token validation or do not verify the token on the server side
  3. Check Referer and Origin header validation
    Review the application server configuration or application code to determine if HTTP Referer and Origin headers are validated to confirm request origin before processing state-changing operations.
    Affected if The application does not validate Referer or Origin headers for cross-origin requests
  4. Inspect SameSite cookie configuration
    Examine the session cookies and authentication tokens set by the application. Check the Set-Cookie headers or cookie configuration to determine if the SameSite attribute is set to 'Strict' or 'Lax' for session-related cookies.
    Affected if SameSite attribute is not set or is set to 'None' for session cookies, allowing cross-site cookie transmission

The environment is affected if the installed Oracle Utilities Application Framework version matches one of the affected versions listed AND the application lacks anti-CSRF token validation, header validation, or proper SameSite cookie attributes on state-changing operations.

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 Critical Patch Updates for Oracle Utilities Applications. Implement anti-CSRF tokens on state-changing operations and validate origin/Referer headers. Consider implementing SameSite cookie attributes.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) patch for Oracle Utilities Application Framework; specific fixed version should be obtained from Oracle's official patch documentation

  1. 1. Identify your current Oracle Utilities Application Framework version from the list of affected versions: 4.4.0.3.0, 4.5.0.0.0, 4.5.0.1.1, 4.5.0.1.3, 4.5.0.2.0, 25.4, or 25.10
  2. 2. Navigate to Oracle's Critical Patch Updates and Security Alerts page at oracle.com/security-alerts or search for the April 2026 CPU
  3. 3. Locate the patch for Oracle Utilities Application Framework addressing CVE-2026-21924
  4. 4. Download and apply the appropriate patch for your specific version
  5. 5. Verify the patch was applied successfully by checking the framework version
Caveat Check Oracle's patch documentation for any known issues or prerequisites before applying

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

Fix this in Utilities Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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