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

CVE-2026-3001

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

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
The Gutenverse plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 3.4.6 due to insufficient input sanitization and output escaping. Specifically, the `render_content()` method in `class-search-result-title.php` outputs the value of `get_query_var('s')` directly into the page HTML without applying `esc_html()` or any other escaping function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages via a crafted URL that execute if a user clicks the link, provided the `gutenverse/search-result-title` block is present on the site's search results template.

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

The Gutenverse WordPress plugin reflects the search query parameter 's' directly into HTML without escaping in the render_content() method of class-search-result-title.php. Unauthenticated attackers can inject arbitrary JavaScript via crafted URLs containing malicious script in the 's' parameter, which executes when users click the link if the gutenverse/search-result-title block exists on the search results template.

MitigationUpgrade Gutenverse plugin to version 3.4.7 or later, which applies proper escaping to the search query output. If unable to upgrade immediately, remove the search-result-title block from the search template as a temporary workaround.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Gutenverse plugin installation and version
    Navigate to WordPress admin > Plugins and locate Gutenverse, or check the plugin header file for the version number in wp-content/plugins/gutenverse/ folder
    Affected if Gutenverse is installed and the version is lower than 3.4.7
  2. Confirm the search-result-title block exists in search template
    Access the WordPress site editor (Appearance > Editor), open the search results template, and look for the gutenverse/search-result-title block in the template structure
    Affected if The search-result-title block is present in the search results template
  3. Test reflected XSS via the 's' parameter
    Visit a search page on the site (such as /?s=test) and inspect the page source or use browser developer tools to see if the 's' parameter value is reflected unescaped in the HTML output around the search result titles
    Affected if The search query parameter 's' is reflected directly into HTML without proper escaping (script tags would execute)

A user is affected if Gutenverse version is below 3.4.7 AND the search-result-title block exists on their search results template, allowing unauthenticated XSS via the 's' parameter.

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 Gutenverse plugin to version 3.4.7 or later, which applies proper escaping to the search query output. If unable to upgrade immediately, remove the search-result-title block from the search template as a temporary workaround.

Recommended fix High confidence

Gutenverse plugin version 3.4.7 or later

  1. 1. Identify all WordPress installations using the Gutenverse plugin.
  2. 2. Check the current installed version of the Gutenverse plugin.
  3. 3. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  4. 4. If the installed version is 3.4.6 or earlier, update the plugin to the latest available version.
  5. 5. Verify the update was successful and the plugin is now running a version higher than 3.4.6.
  6. 6. Test the search functionality to confirm the fix works correctly.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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