LiveActive security incident?Get immediate response
CVE Record

CVE-2020-20969: File Upload vulnerability in PluckCMS v.4.7.10 allows a remote attacker to execute arbitrary code via the t...

File Upload vulnerability in PluckCMS v.4.7.10 allows a remote attacker to execute arbitrary code via the trashcan_restoreitem.php file.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-20969 is a high-severity file upload flaw in PluckCMS 4.7.10. A remote attacker with high privileges could abuse trashcan_restoreitem.php to execute arbitrary code. This matters because successful exploitation could compromise site confidentiality, integrity, and availability.

Executive priority

Treat this as a priority for any internet-facing PluckCMS 4.7.10 site. The privilege requirement lowers broad opportunistic risk, but successful abuse could lead to full site compromise.

Technical view

The issue is classified as CWE-434, unrestricted upload of a file with dangerous type. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, indicating network reachability, low attack complexity, high privileges required, and full impact after success.

Likely exposure

Exposure appears limited to PluckCMS 4.7.10 deployments, especially where administrative functionality and the trash restore path are reachable by privileged users. The source bundle does not identify broader affected versions or CPEs.

Exploitation context

The CVE references a GitHub issue and a public proof-of-concept write-up. CISA KEV is false, and the provided sources do not confirm active exploitation in the wild.

Researcher notes

Evidence is sparse. The CVE description names trashcan_restoreitem.php and arbitrary code execution, but the bundle does not provide patch details, affected-version range, or vendor-confirmed remediation. Avoid assuming impact beyond PluckCMS 4.7.10.

Mitigation direction

  • Check Pluck CMS upstream guidance for a fixed release or supported workaround.
  • Upgrade if vendor guidance identifies a patched version.
  • Restrict PluckCMS administrative access to trusted users and trusted networks.
  • Review upload and restore permissions for unnecessary privileged accounts.
  • Inspect existing uploads and restored files for unexpected executable content.

Validation and detection

  • Inventory PluckCMS sites and confirm whether version 4.7.10 is present.
  • Verify whether trashcan_restoreitem.php is reachable from untrusted networks.
  • Review administrative account access for unnecessary high-privilege users.
  • Check web server logs for unusual restore or upload activity.
  • Confirm remediation against vendor guidance, not assumptions.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-20969 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2020-20969Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.