dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57651

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 8 weeks old

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
Contributor Cross Site Scripting (XSS) in Ghost Kit <= 3.6.0 versions.

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 · moderate confidence

A Cross Site Scripting (XSS) vulnerability exists in the Ghost Kit WordPress plugin (versions <= 3.6.0) that allows users with Contributor-level privileges to inject malicious scripts. The vulnerability stems from insufficient input sanitization or output encoding in the plugin, potentially allowing script execution when the crafted payload is rendered in the browser.

MitigationUpdate Ghost Kit to the latest version available from the vendor, which should contain proper input sanitization and output encoding to prevent XSS attacks. If no update is available, consider removing or disabling the plugin until a patch is released.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Verify Ghost Kit plugin is installed
    Check the WordPress plugins directory (/wp-content/plugins/) for the ghost-kit folder, or query the wp_plugins database table for an entry with plugin_name containing 'Ghost Kit'
    Affected if The ghost-kit folder exists in the plugins directory or the plugin is found in the WordPress database
  2. Determine installed Ghost Kit version
    Access WordPress admin > Plugins > Ghost Kit and view the version number, or read the main plugin file header in /wp-content/plugins/ghost-kit/ to extract the 'Version' tag
    Affected if The installed version is 3.6.0 or any earlier version (versions <= 3.6.0 are affected)
  3. Confirm WordPress user roles with Contributor access
    Navigate to WordPress admin > Users and review the role assigned to each user. Contributor role grants the privileges needed to trigger this vulnerability
    Affected if Any user account has the Contributor role (or higher roles), as these can exploit the XSS flaw

Your environment is affected if Ghost Kit plugin is installed with version 3.6.0 or lower and your WordPress site has users with Contributor-level or higher access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ghost Kit to the latest version available from the vendor, which should contain proper input sanitization and output encoding to prevent XSS attacks. If no update is available, consider removing or disabling the plugin until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57651 — 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-57651 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