Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege staff user
-
ExploitObtain valid staff token
-
ExecutionIssue post-edit API request beyond privilege
-
ImpactModify restricted posts (integrity impact)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid, already-provisioned low-privilege Ghost staff account (PR:L) - e.g. Author or Contributor roles - on an instance running Ghost 4.3.0 through 6.57.x. The attacker leverages staff tokens to send post-editing API requests that exceed their assigned role's permissions. No user interaction is needed (UI:N) and the vector is network-reachable, but exploitation is gated by holding staff credentials; it is not reachable by anonymous/unauthenticated internet users. Impact is limited to unauthorized modification of post content (integrity), with no disclosure or availability effect. |
| Impact | This is a moderate, authenticated-only authorization flaw - not a widespread-exploitation priority. The CVSS 4.0 vector (5.3, AV:N/AC:L/AT:N/PR:L/UI:N) confirms network reach with low complexity but requires existing low-privilege staff credentials (PR:L), and impact is confined to integrity (VI:L) with no confidentiality or availability effect - consistent with CWE-863 (incorrect authorization). No EPSS score, no CISA KEV listing, and no public exploit code were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The practical risk is insider/privilege-boundary abuse within an organization's own staff, not mass internet-facing compromise. The input label 'Authentication Bypass' overstates the nature of the issue: the CWE (863) and description describe an authenticated staff user exceeding their authorization, not bypassing authentication - this mislabeling should not be read as a login-bypass. Overall a real but low-urgency issue; patch during normal maintenance. |
| Exploit ScenarioDerived | A legitimately provisioned low-privilege Ghost staff account (e.g. Author or Contributor) obtains or reuses a valid staff token and issues API requests to edit posts the account should not be permitted to modify, exceeding its assigned editorial privilege. No public exploit code is referenced, and exploitation requires already holding valid staff credentials on the instance. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Authenticated low-privilege staff users on Ghost CMS versions 4.3.0 through 6.57.x can abuse staff tokens to modify posts beyond the permissions granted to their role, effectively bypassing the post-editing restrictions that separate Authors and Contributors from higher-privileged editors. Exploitation requires a valid, already-provisioned staff account (PR:L in both the reported and independently assessed vectors), so it is not reachable by anonymous internet users, and the impact is confined to unauthorized content modification (integrity) with no data disclosure or availability loss. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is a moderate, authenticated-only authorization flaw rather than a widespread-exploitation priority; a vendor patch is available from Ghost in version 6.58.0.
RemediationAI
Vendor-released patch: upgrade Ghost to version 6.58.0 or later, the first release that fixes the incorrect authorization on staff-token post editing, per the vendor advisory GHSA-jj85-wvj2-r86m (https://github.com/TryGhost/Ghost/security/advisories/GHSA-jj85-wvj2-r86m); patch availability is confirmed by the vendor and echoed in the VulnCheck advisory (https://www.vulncheck.com/advisories/ghost-4.3.0-before-6.58.0-incorrect-authorization-via-staff-token). Until upgrading, apply compensating controls: audit all staff accounts and downgrade or remove any unnecessary Contributor/Author roles so that only trusted people hold tokens capable of reaching post-editing endpoints (side effect: reduced editorial throughput); rotate or revoke existing staff tokens and API keys so previously issued low-privilege tokens cannot be reused, accepting the operational cost of re-authentication for legitimate staff; and monitor Ghost Admin API logs for post-edit requests submitted by accounts whose role should not permit them, which can detect abuse but does not prevent it. Because exploitation requires valid staff credentials, tightening account provisioning and enforcing least privilege materially reduces exposure even before the upgrade is deployed.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an instance of CWE-863 (Incorrect Authorization) in the Ghost publishing platform, tracked by the vendor as GHSA-jj85-wvj2-r86m. The root cause is that Ghost's authorization checks on post-editing operations do not adequately validate that the calling staff token belongs to a user whose role actually permits the requested edit; a token issued to a lower-privilege staff member can therefore be used against Admin API endpoints to reach editing functionality reserved for more privileged roles. The affected technology is the Ghost Admin API and its staff-token-based authentication model, where roles such as Contributor (draft-only), Author (own posts) and Editor/Administrator (broader editing) are distinguished. Because the check is authorization-level rather than cryptographic, the token itself is valid - the request simply is not constrained to the privilege level of its owner. The CPE cpe:2.3:a:tryghost:ghost:*:*:*:*:*:*:*:* confirms the affected component is the core tryghost:ghost product, and the EUVD entry (EUVD-2026-90666) independently records the 4.3.0 < 6.58.0 affected range, matching the vendor advisory and the VulnCheck report.
Know when Ghost gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Authenticated low-privilege staff account required (PR:L), network vector with low complexity, and impact limited to unauthorized post edits so I:L with C:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
Ghost versions 4.3.0 before 6.58.0 contain an authentication bypass vulnerability where lower-privilege staff users can use staff tokens to bypass post editing restrictions. Attackers with staff credentials can leverage tokens to edit posts beyond their assigned privilege level.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Ghost CMS versions 5.105.0-5.130.5 and 6.0.0-6.10.3 contain an authentication bypass in their two-factor authentication
Arbitrary code execution in Ghost CMS versions 0.7.2 through 6.19.0 allows authenticated attackers with theme upload pri
An arbitrary file upload vulnerability in the file upload module of Ghost CMS v4.42.0 allows attackers to execute arbitr
An arbitrary file upload vulnerability in the file upload module of Ghost v4.39.0 allows attackers to execute arbitrary
SQL injection in Ghost CMS versions 3.24.0 through 6.19.0 allows unauthenticated attackers to read arbitrary database da
Ghost through 5.85.1 allows remote attackers to bypass an authentication rate-limit protection mechanism by using many X
Ghost through 5.76.0 allows stored XSS, and resultant privilege escalation in which a contributor can take over any acco
Ghost before 5.82.0 allows CSV Injection during a member CSV export. Rated high severity (CVSS 8.8), this vulnerability
Server-side request forgery (SSRF) vulnerability in Ghost CMS < 3.10.0 allows an attacker to scan local or external netw
Ghost before 5.42.1 allows remote attackers to read arbitrary files within the active theme's folder via /assets/built%2
Ghost is a Node.js CMS. Rated medium severity (CVSS 6.8), this vulnerability is remotely exploitable, no authentication
Ghost is an open source content management system. Rated medium severity (CVSS 6.5), this vulnerability is remotely expl
EUVD-2026-90666
GHSA-3qxh-9f4j-4rwp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB