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.
CVE-2026-103273
Score 4.3 from GitHub Security Advisory published 2026-10-01. A secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.3
- EG Score
- 4.3MEDIUMhigh confidence
- EG Risk
- 19EG Risk 19/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 15th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 1, 2026
Last Modified
October 1, 2026
Advisory Details (2)
Auto-updated Oct 1, 2026Ghost 4.3.0 before 6.58.0 Incorrect Authorization via Staff Token | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ghost-4.3.0-before-6.58.0-incorrect-authorization-via-staff-tokenStaff Tokens Granted Elevated Post Privileges · Advisory · TryGhost/Ghost · GitHub
https://github.com/TryGhost/Ghost/security/advisories/GHSA-jj85-wvj2-r86mVendor Advisories for CVE-2026-103273(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 13:34 UTCEG score recompute
- 2026-10-03 13:34 UTCGHSA enrichment
- 2026-10-02 14:25 UTCGHSA enrichment
- 2026-10-01 15:13 UTCGHSA enrichment
- 2026-10-01 14:21 UTCEG score recompute
- 2026-10-01 14:21 UTCGHSA enrichment
- 2026-10-01 13:41 UTCEG score recompute
- 2026-10-01 13:41 UTCGHSA enrichment
- 2026-10-01 11:26 UTCEG score recompute
- 2026-10-01 10:51 UTCEG score recompute
- 2026-10-01 10:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-103273?
When was CVE-2026-103273 disclosed?
Is CVE-2026-103273 actively exploited?
What is the CVSS score of CVE-2026-103273?
How do I remediate CVE-2026-103273?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-103273
Is Your Infrastructure Affected by CVE-2026-103273?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.