dbcve.org
Agile Product Lifecycle Management For ProcessApplication · Oracle

CVE-2026-21944

MEDIUM · 6.8 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 →
72/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 Agile Product Lifecycle Management for Process product of Oracle Supply Chain (component: Product Quality Management). The supported version that is affected is 6.2.4. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Agile Product Lifecycle Management for Process. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Agile Product Lifecycle Management for Process accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 · high confidence

A vulnerability in Oracle Agile PLM for Process (Product Quality Management component version 6.2.4) allows low-privileged attackers with network access via HTTP to read sensitive data due to insufficient authorization checks. The CVSS vector indicates a confidentiality-only impact with high data exposure but no integrity or availability compromise.

MitigationApply Oracle's security patches for this vulnerability and review/limit user permissions in the Product Quality Management module to enforce proper authorization controls.

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
Agile Product Lifecycle Management For ProcessApplication
Affected:= 6.2.4

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/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. Confirm Oracle Agile PLM for Process is installed
    Locate the installation directory or check system inventory for 'Oracle Agile PLM for Process' or 'Agile Process' software. On Windows, check Add/Remove Programs. On Linux, check installed packages or application directories.
    Affected if The software is present on the system
  2. Verify the exact version is 6.2.4
    Check the version of Oracle Agile PLM for Process. This can typically be found in the application's About section, in the installation directory's version file, or via the application's help > about menu. Common paths include the /bin or /version directories within the Oracle Agile installation.
    Affected if The installed version is exactly 6.2.4
  3. Confirm Product Quality Management module is accessible
    Log into the Oracle Agile PLM for Process web interface and navigate to check if the Product Quality Management module is available. This is typically accessed through the application's main menu or module selection screen.
    Affected if The Product Quality Management module is present and accessible to the user account being tested
  4. Verify HTTP network accessibility
    Confirm the application is accessible over HTTP/HTTPS by attempting to reach the application's web URL. Check if the application's HTTP endpoint is exposed on the network.
    Affected if The application is reachable via network HTTP/HTTPS access
  5. Test low-privilege user access to sensitive data
    Using a low-privileged user account (non-admin), attempt to access data within the Product Quality Management module that should normally be restricted. Observe if unauthorized data is returned or accessible.
    Affected if A low-privileged user can read sensitive data they should not have access to within the Product Quality Management module

The environment is affected if Oracle Agile PLM for Process version 6.2.4 is installed with the Product Quality Management module accessible over HTTP, and low-privileged users can read restricted data due to insufficient authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patches for this vulnerability and review/limit user permissions in the Product Quality Management module to enforce proper authorization controls.

Fix this in Agile Product Lifecycle Management For Process Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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