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

CVE-2026-56040

HIGH · 7.1 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 →
78/100
Remediation priority · High
Remotely reachable No privileges 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
Unauthenticated Cross Site Scripting (XSS) in Gutenverse Form <= 2.4.7 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

Unauthenticated Cross-Site Scripting (XSS) vulnerability in the Gutenverse Form WordPress plugin affecting versions 2.4.7 and below. An attacker can inject malicious JavaScript through form inputs without authentication, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationUpdate Gutenverse Form plugin to a version newer than 2.4.7 to patch the XSS vulnerability. If immediate update is not possible, consider disabling the plugin until the patch can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Gutenverse Form plugin is installed
    Navigate to WordPress admin Dashboard > Plugins > Installed Plugins. Look for 'Gutenverse Form' in the list of installed plugins.
    Affected if Gutenverse Form plugin appears in the installed plugins list
  2. Check the installed version of Gutenverse Form
    In the plugins list, click on 'Gutenverse Form' to view plugin details, or open the main plugin file (gutenverse-form.php) in wp-content/plugins/gutenverse-form/ and locate the 'Version:' header comment.
    Affected if The displayed version number is 2.4.7 or lower
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins. Verify that Gutenverse Form shows as 'Active' rather than 'Inactive' or 'Deactivated'.
    Affected if Gutenverse Form is currently activated on the site
  4. Check for publicly accessible Gutenverse forms
    Visit your website frontend and navigate to pages containing Gutenverse form blocks or shortcodes. Look for any input fields rendered by the plugin.
    Affected if Public-facing pages contain Gutenverse Form inputs that can be accessed without authentication

If Gutenverse Form plugin is installed, active, version 2.4.7 or below, and has forms accessible on the frontend, the environment is vulnerable to this unauthenticated XSS.

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 Gutenverse Form plugin to a version newer than 2.4.7 to patch the XSS vulnerability. If immediate update is not possible, consider disabling the plugin until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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