Security readout for executives and security teams
Plain-English summary
PluckCMS 4.7.4 and earlier could accept a dangerous uploaded file as an image when the request MIME type is manipulated. The CVE states the impact is obtaining a webshell, which can give an attacker control over the affected website.
Executive priority
Treat this as high priority for any public or business-critical PluckCMS site, because the documented impact is webshell access. Prioritize patch verification and exposure review over broad emergency response unless local evidence of compromise appears.
Technical view
CVE-2019-1010062 is a CWE-434 unrestricted upload issue in PluckCMS data/inc/images.php, identified at line 36 in the CVE description. Affected versions are 4.7.4 and earlier. The listed fix is after commit 09f0ab871bf633973cfd9fc4fe59d4a912397cf8.
Likely exposure
Exposure is limited to deployments running PluckCMS 4.7.4 or earlier with reachable image upload functionality. The bundle provides no CPEs, CVSS vector, or hosting-context details.
Exploitation context
The source bundle describes MIME type manipulation to upload a PHP file and states the impact as webshell access. It does not cite active exploitation, and the CVE is not listed as KEV.
Researcher notes
Evidence is concise but direct: CWE-434, affected PluckCMS ≤4.7.4, component data/inc/images.php line 36, and a named fixing commit. CVSS and exploitation-in-the-wild evidence are absent from the provided bundle.
Mitigation direction
- Upgrade to a PluckCMS version containing commit 09f0ab871bf633973cfd9fc4fe59d4a912397cf8 or later.
- Review vendor project guidance for supported fixed releases and migration notes.
- Restrict access to upload functionality until the fixed build is deployed.
- Inspect uploaded content directories for unexpected executable files.
Validation and detection
- Inventory PluckCMS installations and confirm whether any are version 4.7.4 or earlier.
- Verify the deployed code includes commit 09f0ab871bf633973cfd9fc4fe59d4a912397cf8 or later.
- Review upload directories and web logs for suspicious file uploads.
- Confirm upload handling no longer permits dangerous server-executable file types.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2019-1010062 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pluck-cms/pluck/commit/09f0ab871bf633973cfd9fc4fe59d4a912397cf8CVE reference · x_refsource_MISC
- https://github.com/pluck-cms/pluck/issues/44CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.