Ghost versions 0.5.0 before 6.23.0 contain a concurrency issue in the staff invitation acceptance mechanism that allows multiple accounts to be created from a single invite token. Attackers can exploit this race condition by submitting concurrent requests with the same invitation token to create duplicate user accounts.
CVE-2026-103282
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.1%
- EPSS %ILE
- 2nd
- 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 0.5.0 before 6.23.0 Multiple Account Creation via Invite Token | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ghost-0.5.0-before-6.23.0-multiple-account-creation-via-invite-tokenInvite Tokens could be Used Multiple Times · Advisory · TryGhost/Ghost · GitHub
https://github.com/TryGhost/Ghost/security/advisories/GHSA-vf9h-87xm-g767Vendor Advisories for CVE-2026-103282(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 13× in last 7d / 13× 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 17:43 UTCEG score recompute
- 2026-10-03 17:43 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 16:34 UTCEG score recompute
- 2026-10-02 16:34 UTCGHSA enrichment
- 2026-10-01 15:23 UTCGHSA enrichment
- 2026-10-01 15:12 UTCEG score recompute
- 2026-10-01 15:12 UTCGHSA enrichment
- 2026-10-01 14:51 UTCEG score recompute
- 2026-10-01 14:51 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-103282?
When was CVE-2026-103282 disclosed?
Is CVE-2026-103282 actively exploited?
What is the CVSS score of CVE-2026-103282?
How do I remediate CVE-2026-103282?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-103282
Is Your Infrastructure Affected by CVE-2026-103282?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.