dbcve.org
Primavera P6 Enterprise Project Portfolio ManagementApplication · Oracle

CVE-2025-21558

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to after 21.12.20.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 and 22.12.1.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

A vulnerability in the Web Access component of Oracle Primavera P6 Enterprise Project Portfolio Management allows authenticated low-privilege attackers with network access to perform unauthorized read, insert, update, and delete operations on a subset of accessible data through the web interface. Exploitation requires human interaction (such as tricking a user into clicking a malicious link or visiting a crafted page).

MitigationApply the Oracle Critical Patch Update that addresses CVE-2025-21558, or upgrade to a patched version beyond the affected version ranges (22.12.1.0 or later for the 22.x line).

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

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. Confirm Oracle Primavera P6 EPPM installation
    Locate the P6 installation directory and check for Primavera P6 Enterprise Project Portfolio Management. Look for P6 EPPM-specific configuration files or the P6 Professional/Admin console to verify the product edition.
    Affected if The target system is NOT Oracle Primavera P6 Enterprise Project Portfolio Management (this vulnerability only affects that specific product)
  2. Identify installed P6 EPPM version
    Access the P6 Administrator or P6 Professional application, or check the About section in the P6 web interface. The version is typically displayed in the format XX.xx.x.x (e.g., 20.12.1.0, 21.12.1.0, 22.12.1.0).
    Affected if The installed version falls within 20.12.1.0 to 20.12.21.5 inclusive, OR 21.12.1.0 to 21.12.20.0 inclusive, OR equals exactly 22.12.1.0
  3. Verify Web Access component is enabled
    Check the P6 EPPM configuration for the Web Access or P6 Web Gateway component. This is typically configured through P6 Administrator or the web server configuration (Oracle WebLogic, Apache, IIS). Look for enabled web endpoints accessible via HTTP/HTTPS.
    Affected if The Web Access component is enabled and accessible (the vulnerability exists in this component)
  4. Confirm network accessibility of web interface
    Test connectivity to the P6 web interface URLs (typically port 80/443 or custom ports). Use browser or command-line tools like curl to verify the web application is reachable over the network.
    Affected if The P6 web interface is network-accessible (attackers require network access to exploit this flaw)
  5. Review user account configuration
    Check P6 EPPM user management for the presence of low-privilege user accounts. Examine user roles and permissions in P6 Administrator or the web interface user management section.
    Affected if There are authenticated users with network access to the web interface, particularly accounts with limited privileges (exploitation targets low-privilege authenticated users)

You are affected if the installed Oracle Primavera P6 EPPM version is within 20.12.1.0-20.12.21.5, 21.12.1.0-21.12.20.0, or exactly 22.12.1.0 AND the Web Access component is enabled and network-accessible to authenticated 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
Upgrade available Upgrade to a release after 21.12.20.0
Interim mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2025-21558, or upgrade to a patched version beyond the affected version ranges (22.12.1.0 or later for the 22.x line).

Recommended fix Moderate confidence

Upgrade to 20.12.22+, 21.12.21+, or 22.12.2+ (depending on your current version branch)

  1. 1. Identify the current installed version of Primavera P6 Enterprise Project Portfolio Management.
  2. 2. Determine which version branch your installation falls under (20.12.x, 21.12.x, or 22.12.x).
  3. 3. Access Oracle Support and search for Oracle Critical Patch Update (CPU) advisory for January 2025 or later that addresses CVE-2025-21558.
  4. 4. Download and apply the relevant patch for your specific version from Oracle.
  5. 5. Alternatively, upgrade to a version beyond the last affected version in your branch: for 20.12.x line upgrade to 20.12.22 or later; for 21.12.x line upgrade to 21.12.21 or later; for 22.12.x line upgrade to 22.12.2 or later.
  6. 6. After applying patch or upgrade, restart all P6 services.
  7. 7. Verify the fix by logging in as a low-privileged user and confirming that unauthorized data access is no longer possible.
Caveat Review Oracle's upgrade documentation for your version branch as minor version upgrades may include database schema changes requiring migration steps

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

Fix this in Primavera P6 Enterprise Project Portfolio Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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