Security readout for executives and security teams
Plain-English summary
Pluck CMS versions before 4.7.7-dev2 had an upload handling flaw that could let a remote attacker get PHP code executed on the web server. For an affected public website, this could become full site compromise. The provided sources do not state active exploitation.
Executive priority
Prioritize remediation for any internet-facing Pluck CMS instance. Even without confirmed active exploitation, the documented impact is remote code execution, which can expose website data, credentials, and hosting infrastructure.
Technical view
The issue is in Pluck's /data/inc/images.php upload path before 4.7.7-dev2. The CVE states attackers could abuse image upload handling and content-type trust to place server directives that enable PHP execution. CVSS and CWE metadata are not provided in the source bundle.
Likely exposure
Exposure is likely limited to websites running Pluck CMS before 4.7.7-dev2. The sources do not provide CPEs, deployment prevalence, or authentication requirements, so asset owners should verify installed Pluck versions directly.
Exploitation context
The source bundle supports remote arbitrary PHP execution potential, but does not cite public exploitation in the wild. CISA KEV status is false in the provided data. Treat internet-facing affected installations as urgent to review because code execution can lead to takeover.
Researcher notes
Evidence is concise but primary: CVE text names the vulnerable file, affected version boundary, and execution impact. Missing details include authentication preconditions, CVSS score, CWE mapping, and exact patch mechanics. Avoid assuming broader Pluck versions beyond before 4.7.7-dev2.
Mitigation direction
- Upgrade Pluck CMS to 4.7.7-dev2 or a later vendor-supported release.
- Review the linked GitHub issue and release notes for vendor-specific guidance.
- Restrict access to Pluck administrative and upload functionality where operationally possible.
- Inspect uploaded content directories for unexpected server configuration or PHP-enabling files.
- Back up and investigate any affected host before restoring normal exposure.
Validation and detection
- Inventory all public and internal sites running Pluck CMS.
- Confirm each Pluck installation version is 4.7.7-dev2 or later.
- Review web roots and upload directories for unexpected configuration or executable content.
- Check web server logs around image upload endpoints for suspicious requests.
- Verify upload handling no longer accepts unsafe server configuration files.
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.
CVE-2018-11736 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/issues/61CVE reference · x_refsource_CONFIRM
- https://github.com/pluck-cms/pluck/releases/tag/4.7.7-dev2CVE reference · x_refsource_CONFIRM
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.