Security readout for executives and security teams
Plain-English summary
WolfCMS 0.8.3.1 allowed a lower-privileged CMS user to store script content in a layout name. If an administrator later viewed that content, the attacker could potentially steal the admin cookie and take over the admin account.
Executive priority
Treat this as a targeted CMS administration risk, not a broad internet worm risk. Prioritize if WolfCMS is still used for business-facing content or if non-admin users have CMS access.
Technical view
The CVE describes stored cross-site scripting in the WolfCMS Layout tab, specifically the Layout Name field, affecting version 0.8.3.1. The reported impact is admin cookie theft and admin account compromise from attacker-controlled JavaScript stored by a low-privilege user.
Likely exposure
Exposure is likely limited to organizations still running WolfCMS 0.8.3.1 with untrusted or lower-privileged users able to create or edit layouts.
Exploitation context
The source states exploitation requires entering JavaScript into the Layout Name field. There is no KEV listing and no cited evidence of active exploitation in the provided sources.
Researcher notes
The public record is sparse: no CVSS, CWE, CPE, or patch details are provided in the bundle. The affected product is named in the description, but structured affected metadata is incomplete.
Mitigation direction
- Identify any WolfCMS 0.8.3.1 deployments.
- Check WolfCMS project guidance or issue history for a confirmed fixed version.
- Restrict layout creation and editing to trusted administrators only.
- Review layout names and recent layout changes for suspicious script content.
- Retire or migrate unsupported WolfCMS instances where no maintained fix is available.
Validation and detection
- Confirm the deployed WolfCMS version from application inventory or host records.
- Audit CMS user roles with access to the Layout tab.
- Inspect existing layout names for unexpected HTML or script-like content.
- Review logs for layout edits followed by unusual admin session activity.
- Document whether vendor guidance confirms a patch or workaround.
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-1000084 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/wolfcms/wolfcms/issues/667CVE 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.