dbcve.org
Primavera P6 Enterprise Project Portfolio ManagementApplication · Oracle

CVE-2025-21526

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to after 23.12.10.0 or later.
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 Primavera P6 Enterprise Project Portfolio Management product of Oracle Construction and Engineering (component: Web Access). Supported versions that are affected are 20.12.1.0-20.12.21.5, 21.12.1.0-21.12.20.0, 22.12.1.0-22.12.16.0 and 23.12.1.0-23.12.10.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Primavera P6 Enterprise Project Portfolio Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Primavera P6 Enterprise Project Portfolio Management, 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 Primavera P6 Enterprise Project Portfolio Management accessible data as well as unauthorized read access to a subset of Primavera P6 Enterprise Project Portfolio Management 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 · high confidence

Vulnerability in Oracle Primavera P6 Enterprise Project Portfolio Management's Web Access component allows low-privileged attackers with network access via HTTP to compromise the system. The flaw permits unauthorized read, insert, update, and delete access to a subset of application data. Exploitation requires human interaction from a person other than the attacker, and the vulnerability scope may extend to additional products.

MitigationApply the relevant Oracle Critical Patch Update for Primavera P6. Until patches are applied, restrict network access to the Web Access component and implement WAF rules to filter malicious HTTP requests.

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
Primavera P6 Enterprise Project Portfolio ManagementApplication
Affected:>= 20.12.1.0, <= 20.12.21.5>= 21.12.1.0, <= 21.12.20.0>= 22.12.1.0, <= 22.12.16.0>= 23.12.1.0, <= 23.12.10.0

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 if Oracle Primavera P6 EPPM is installed
    Check for the P6 installation directory, typically under OracleMiddleware or Oracle product directories on the server (e.g., $ORACLE_HOME/primera), or look for the P6 services running on the application server.
    Affected if The product is not installed or only standalone client versions exist (this CVE affects the Enterprise Project Portfolio Management component only).
  2. Determine the installed P6 EPPM version
    Locate the version file or check the P6 database version table. The version is typically shown in the P6 Web Access login page footer, or can be queried from the database (e.g., SELECT version FROM admin_version). Compare against affected ranges: 20.12.1.0-20.12.21.5, 21.12.1.0-21.12.20.0, 22.12.1.0-22.12.16.0, or 23.12.1.0-23.12.10.0.
    Affected if The installed version falls within any of the four affected version ranges.
  3. Verify the Web Access component is enabled and exposed
    Confirm that the P6 Web Access (p6webaccess) application is deployed and accessible. Check the application server (WebLogic, etc.) for the p6webaccess deployment status and verify it is listening on an HTTP port accessible to network attackers.
    Affected if The Web Access component is deployed and reachable over HTTP/HTTPS from the network.
  4. Check for low-privileged user accounts
    Review the P6 user management to confirm whether low-privileged user accounts exist in the system, as the vulnerability allows attacks using such accounts.
    Affected if Non-admin user accounts are present in the P6 application (the vulnerability exploitation requires using low-privileged credentials).

You are affected if Oracle Primavera P6 EPPM with Web Access enabled is installed and its version falls within any of the four affected ranges (20.12.x, 21.12.x, 22.12.x, or 23.12.x up to the respective upper limits).

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
Upgrade available Upgrade to a release after 23.12.10.0
Interim mitigation

Apply the relevant Oracle Critical Patch Update for Primavera P6. Until patches are applied, restrict network access to the Web Access component and implement WAF rules to filter malicious HTTP requests.

Fix this in Primavera P6 Enterprise Project Portfolio Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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