dbcve.org
CWE-204Weakness · CWE-204

CVE-2026-53947

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Ghost is a Node.js content management system. From 5.18.0 until 6.21.1, a discrepancy in responses from the members signin endpoints made it possible for an unauthenticated attacker to determine whether a given email address belongs to a registered member of a Ghost site. This vulnerability is fixed in 6.21.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Ghost CMS versions 5.18.0 through 6.21.1 contain an information disclosure vulnerability in the members signin endpoint. The endpoint returns different responses (timing, error messages, or behavior) for registered vs. unregistered email addresses, allowing unauthenticated user enumeration. An attacker can determine if a specific email is registered as a member on the site.

MitigationUpgrade Ghost to version 6.21.1 or later, which contains the fix for consistent endpoint responses. Additionally, implement rate limiting on authentication endpoints to further mitigate enumeration attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ghost CMS version
    Run 'ghost version' in the installation directory, or check the 'package.json' file in the Ghost root folder for the version number
    Affected if The installed version is 5.18.0 through 6.21.1 inclusive
  2. Verify members feature is enabled
    Check the Ghost config file (config.production.json) for the 'members' setting under 'labs' or review the site's members settings in the admin panel at /ghost/#/settings/members
    Affected if Members signup/signin is enabled (default behavior allows this enumeration vector)
  3. Confirm signin endpoint is accessible
    Attempt to access the members signin endpoint at '/members/api/signin/' or check if routes.yaml exposes the members API without authentication requirements
    Affected if The endpoint responds to unauthenticated requests (no authentication required to trigger the enumeration)
  4. Test endpoint response differentiation (if feasible)
    Send two POST requests to the signin endpoint with different emails (one known registered, one unknown) and compare HTTP status codes, response times, or error messages
    Affected if The endpoint returns measurably different responses (timing, status, or message content) between registered and unregistered emails

A system is affected if it runs Ghost CMS version 5.18.0 through 6.21.1 with members functionality enabled and the signin endpoint accessible to unauthenticated users, allowing response-based email enumeration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Ghost to version 6.21.1 or later, which contains the fix for consistent endpoint responses. Additionally, implement rate limiting on authentication endpoints to further mitigate enumeration attempts.

Recommended fix High confidence

6.21.1

  1. 1. Backup your Ghost site database and content files before upgrading.
  2. 2. Check your current Ghost version using `ghost version` or by viewing the version in your Ghost admin panel.
  3. 3. Run `ghost update` to upgrade to the latest version, or specify `ghost update v6.21.1` to upgrade to the specific fixed release.
  4. 4. Verify the upgrade was successful by running `ghost version` and confirming it shows 6.21.1.
  5. 5. Test the members signin endpoint to confirm the vulnerability is remediated - the endpoint should now return consistent responses regardless of whether the email exists.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data