CVE-2020-14706
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 17.1.0.0-17.12.17.1, 18.1.0.0-18.8.19 and 19.12.0-19.12.5. Difficult to exploit vulnerability allows unauthenticated 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Primavera P6 Enterprise Project Portfolio Management accessible data as well as unauthorized update, insert or delete access to some of Primavera P6 Enterprise Project Portfolio Management accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/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 confidenceUnauthenticated HTTP vulnerability in Primavera P6 Enterprise Project Portfolio Management's Web Access component. The flaw allows remote attackers to compromise the application without credentials, though successful exploitation requires human interaction from a victim (indicative of a CSRF or similar request-forgery attack). Attackers can gain unauthorized access to critical data or full data access, plus unauthorized modification capabilities.
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>= 17.1.0.0, <= 17.12.17.1>= 18.1.0.0, <= 18.8.19.0>= 19.12.0.0, <= 19.12.5.0CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/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.
-
Verify Primavera P6 EPPM installationAccess the application server or check for the Primavera P6 web application URL. Look for the P6 Web Access login page or admin console.Affected if The Primavera P6 web application is accessible and responding on HTTP/HTTPS ports.
-
Determine installed P6 versionLog into the P6 administration or about page, or check the Oracle Primavera documentation for version lookup via the web interface or installed binaries.Affected if The version falls within any of these ranges: 17.1.0.0 to 17.12.17.1, 18.1.0.0 to 18.8.19.0, or 19.12.0.0 to 19.12.5.0.
-
Confirm Web Access component is enabledCheck the P6 configuration or administration console for the Web Access component status. Verify the application is accessible via browser without requiring authentication initially.Affected if The Web Access component is enabled and accessible without requiring authentication on the HTTP interface.
-
Inspect for unauthorized data access or modificationReview P6 audit logs, access logs, and data change history for suspicious unauthorized actions, especially those originating from external IP addresses or performed without proper authentication tokens.Affected if Audit logs show data access or modifications performed without valid authentication or anti-CSRF tokens.
You are affected if Primavera P6 EPPM with Web Access is running a version within 17.1.0.0-17.12.17.1, 18.1.0.0-18.8.19.0, or 19.12.0.0-19.12.5.0 and the web interface is accessible without authentication.
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 Oracle's October 2020 Critical Patch Update for Primavera P6, upgrading to a version beyond 19.12.5. As an interim control, implement anti-CSRF tokens and SameSite cookie attributes if supported by the application.
- Consultation4.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA6.0 h
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 locallyCheck whether your project pulls in CVE-2020-14706 — 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-14706 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