Security readout for executives and security teams
Plain-English summary
CVE-2018-11330 affects Pluck CMS versions before 4.7.6. An authenticated user could store JavaScript through a filename because filename characters were not restricted properly. This is primarily a risk to sites where untrusted or lower-privileged CMS users can upload or manage files.
Executive priority
Treat this as a medium-priority web content management risk. Prioritize remediation if Pluck is internet-facing, supports multiple CMS users, or handles sensitive sessions. The available evidence does not support emergency exploitation claims.
Technical view
The vulnerability is authenticated stored cross-site scripting in Pluck before 4.7.6. The CVE description attributes the issue to insufficient filename character-set restrictions. The public bundle provides no CVSS score, CWE mapping, detailed affected package metadata, or evidence of unauthenticated exploitation.
Likely exposure
Exposure is most likely on Pluck CMS deployments older than 4.7.6, especially where multiple users can authenticate and manage files. Single-admin sites have lower practical exposure but still risk account misuse or session impact if stored script executes in an administrator context.
Exploitation context
The source bundle says the issue requires authentication and is stored XSS. CISA KEV status is false, and the provided sources do not claim active exploitation. No exploit maturity, attack prevalence, or public weaponization evidence is included.
Researcher notes
The public record is sparse. The strongest facts are affected version boundary, authenticated stored XSS class, and filename character-set root cause. Confirm details against the linked GitHub issue and commit before assigning exploitability beyond authenticated CMS access.
Mitigation direction
- Upgrade affected Pluck CMS deployments to 4.7.6 or later per vendor guidance.
- Restrict CMS administrator and file-upload privileges to trusted accounts.
- Review uploaded filenames and remove suspicious content after preserving evidence.
- Monitor the linked Pluck issue and commit for implementation-specific guidance.
Validation and detection
- Inventory Pluck CMS instances and record exact installed versions.
- Check whether any deployment runs a version earlier than 4.7.6.
- Review CMS accounts with file-management or upload permissions.
- Inspect recent uploaded filenames for unusual characters without opening untrusted content in privileged sessions.
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.
CVE-2018-11330 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/58CVE reference · x_refsource_MISC
- https://github.com/pluck-cms/pluck/commit/8f6541e60c9435e82e9c531a20cb3c218d36976eCVE 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.