Security readout for executives and security teams
Plain-English summary
Ghost 5.9.4 default installations can let a non-administrator place JavaScript into a post. If an administrator later views that post, the script may run with administrator context, creating a serious privilege-escalation risk.
Executive priority
Treat as high-priority for any Ghost 5.9.4 site with multiple content users. The business risk is administrator takeover through normal editorial review, not unauthenticated remote compromise.
Technical view
The issue is stored XSS in a post's codeinjection_head field. The CVE describes low-privileged post creation as enough to persist arbitrary JavaScript, with administrator viewing required to trigger impact. CVSS 3.0 score is 9.0.
Likely exposure
Exposure is limited to Ghost 5.9.4 deployments, especially default configurations where non-administrator users can create or edit posts that administrators may review.
Exploitation context
The supplied sources do not show known active exploitation, and KEV is false. Exploitation requires an authenticated non-administrator account and administrator interaction with the malicious post.
Researcher notes
Evidence supports stored XSS and privilege escalation in Ghost 5.9.4 default installations. The bundle does not provide CPEs, proof of active exploitation, or a specific fixed version.
Mitigation direction
- Identify and prioritize any Ghost 5.9.4 deployments.
- Check Ghost Foundation and Talos guidance for fixed versions or official mitigations.
- Limit non-administrator post creation to trusted users until remediated.
- Review administrator workflows for untrusted draft or post previews.
Validation and detection
- Confirm the deployed Ghost version on each instance.
- Review whether non-administrator users can create or edit posts.
- Inspect posts for unexpected code injection content.
- Review admin activity after viewing suspicious posts.
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-453: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-47196 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
- Critical
- CVSS
- 9 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 vector scores
1 official scoreWe 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.
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H2.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
9CriticalVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
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.