Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-103272 – Unauthenticated Staff Enumeration / Data Exposure – Ghost 2.10.0 to 6.62.x

Be the first to know when new zero-days emerge:

Summary

CVE-2026-103272 is a staff enumeration and information disclosure vulnerability in Ghost, the open-source publishing and content management platform. The flaw resides in Ghost’s content API, where unauthenticated attackers can analyze discrepancies in API metadata responses to enumerate staff/user accounts and extract sensitive user data. The issue carries a CVSS score of 8.7 (High) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: The content API returns metadata responses that behave differently depending on whether a given staff/user identifier exists or matches certain conditions, creating an observable discrepancy (CWE-203) that also exposes sensitive information through metadata (CWE-1230).
  • Trigger conditions: An attacker sends requests to Ghost’s content API endpoints and compares variations in the metadata responses to infer the existence and details of staff accounts.
  • Attack vector: Network-based; the content API is reachable without authentication, and no user interaction is required.
  • Impact: Confidentiality impact only — unauthorized enumeration of staff members and extraction of associated user data. Integrity and availability of the system are not affected.

Affected software

  • Ghost versions 2.10.0 up to (but not including) 6.63.0

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Ghost to version 6.63.0 or later, which contains the full remediation for this issue.
  • If immediate patching is not possible: Restrict or monitor access to content API endpoints where feasible, and review staff/user account exposure. Network-level mitigations (e.g., WAF rules or rate limiting on content API requests) may reduce the risk of automated enumeration, but should be treated as temporary measures only until the patched version is deployed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge