CVE-2020-14653
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 · uneditedVulnerability in the Primavera P6 Enterprise Project Portfolio Management product of Oracle Construction and Engineering (component: Web Access). Supported versions that are affected are 16.1.0.0-16.2.20.1, 17.1.0.0-17.12.17.1 and 18.1.0.0-18.8.18.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Primavera P6 Enterprise Project Portfolio Management. 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:N/S:U/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 confidenceOracle Primavera P6 Enterprise Project Portfolio Management contains a vulnerability in its Web Access component that allows low-privileged attackers with network access via HTTP to perform unauthorized read, insert, update, and delete operations on a subset of accessible data. The vulnerability affects versions 16.1.0.0 through 18.8.18.2 and is described as easily exploitable.
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>= 16.1.0.0, <= 16.2.20.1>= 17.1.0.0, <= 17.12.17.1>= 18.1.0.0, <= 18.8.18.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Primavera P6 versionAccess the P6 application and navigate to the About section, or check the installation documentation/installer properties. In the P6 web interface, this is typically found under Help > About Oracle Primavera P6. Alternatively, check the P6 professional client or contact your system administrator for the exact version number.Affected if The version falls within 16.1.0.0-16.2.20.1, 17.1.0.0-17.12.17.1, or 18.1.0.0-18.8.18.2
-
Confirm the Web Access component is enabledVerify that P6 Web Access (the web-based interface) is deployed and accessible. Check if the web application server (typically WebLogic or similar) is running and the P6 web application is deployed. This can be confirmed by attempting to access the P6 login page via HTTP/HTTPS.Affected if Web Access is publicly or internally accessible over HTTP and the version is within the affected ranges
-
Verify network accessibility of the Web Access interfaceConfirm that the P6 Web Access URL is reachable from network locations where low-privileged users operate. Check firewall rules, load balancer configurations, and application access controls that permit HTTP/HTTPS traffic to the P6 web application.Affected if The Web Access component is network-accessible to low-privileged users and the version is within the affected ranges
-
Review user access controls for the Web Access componentExamine the P6 user roles and permissions configuration to confirm that low-privileged accounts (non-administrative users) have network access to the Web Access interface. Check if these accounts can perform data operations through the web interface.Affected if Low-privileged users have network access via HTTP to the Web Access component and the version is within the affected ranges
If your installed Oracle Primavera P6 version falls within 16.1.0.0 through 18.8.18.2 and the Web Access component is enabled and network-accessible to low-privileged users, your environment is affected by CVE-2020-14653.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Oracle Critical Patch Update (CPU) for CVE-2020-14653 to the affected Primavera P6 installations. Verify that the patch resolves the vulnerability and conduct post-patch testing to ensure normal functionality.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14653 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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