CVE-2020-2706
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: Project Manager). Supported versions that are affected are 16.2.0.0 - 16.2.19.3, 17.12.0.0 - 17.12.17.0, 18.8.0.0 - 18.8.18.0, 19.12.1.0 - 19.12.3.0 and 20.1.0.0 - 20.2.0.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. 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.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/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 · moderate confidenceInsecure direct object reference or similar access control flaw in Primavera P6's Project Manager component allows authenticated low-privilege users to access or modify data beyond their authorized scope via crafted HTTP requests, requiring human interaction (likely social engineering) for exploitation.
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.2.0.0, <= 16.2.19.3>= 17.12.0.0, <= 17.12.17.0>= 18.8.0.0, <= 18.8.18.0>= 19.12.1.0, <= 19.12.3.0>= 20.1.0.0, <= 20.2.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Primavera P6 versionLocate the version information in the application's About section, admin console, or installation directory metadata. Common paths include the P6 administration settings or the Oracle Primavera P6 database configuration files.Affected if The installed version falls within any of these ranges: 16.2.0.0 to 16.2.19.3, 17.12.0.0 to 17.12.17.0, 18.8.0.0 to 18.8.18.0, 19.12.1.0 to 19.12.3.0, or 20.1.0.0 to 20.2.0.0
-
Confirm Project Manager component is in useCheck if the Project Manager module is enabled in the P6 user roles and permissions configuration. This is typically found in the Administration section under Global Permissions or Project Permissions.Affected if The Project Manager component is active and assigned to users or roles in the system
-
Verify web-based access to P6Confirm that the P6 web interface or web services (which accept HTTP requests) are accessible. This includes checking if P6 Professional Web or P6 EPPM web interfaces are deployed and reachable.Affected if HTTP access to the P6 application is enabled, as exploitation occurs via crafted HTTP requests
-
Audit low-privilege user accountsReview the list of users with authenticated access to P6, specifically those assigned to the Project Manager component. Check for users with limited or restricted role assignments.Affected if Low-privilege authenticated users exist in the system who could potentially leverage the IDOR vulnerability to access unauthorized data
-
Review Project Manager role permissions scopeExamine the permissions assigned to the Project Manager role, specifically whether users can only access projects within their authorized scope. Check for overly broad data access permissions.Affected if Project Manager role permissions allow broader data access than intended, indicating potential misconfiguration that could be exploited
A user is affected if they run a vulnerable version of Primavera P6 EPPM within the listed ranges AND have the Project Manager component enabled with low-privilege users who can send HTTP requests to the application.
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 Critical Patch Update patches for CVE-2020-2706 to affected versions (16.2.x, 17.12.x, 18.8.x, 19.12.x, 20.1-20.2) and review Project Manager role permissions for least-privilege enforcement.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
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 locallyCheck whether your project pulls in CVE-2020-2706 — 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-2706 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