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

CVE-2026-57415

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
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 5 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Codemenschen Gift Vouchers gift-voucher allows Stored XSS.This issue affects Gift Vouchers: from n/a through <= 4.7.0.

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

A stored Cross-site Scripting (XSS) vulnerability exists in the Codemenschen Gift Vouchers plugin where user-supplied input in gift voucher fields is not properly sanitized before being rendered in web pages. An attacker can inject malicious JavaScript that executes in the browsers of users who view the affected voucher content.

MitigationImplement proper input sanitization on all user-supplied voucher fields using WordPress sanitization functions (such as sanitize_text_field, esc_attr, or esc_html) and ensure all output is encoded with appropriate escaping functions before rendering.

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. Identify plugin installation and version
    Locate the Codemenschen Gift Vuzzers plugin in wp-content/plugins/ and read the main plugin file header for the version number, or check the WordPress plugin admin page
    Affected if The installed version falls within the vulnerable version range (check against any known affected versions or assume all versions prior to patch are vulnerable)
  2. Verify plugin is active
    Check WordPress admin under Plugins > Installed Plugins or query the wp_options table for the active_plugins option to confirm the plugin is enabled
    Affected if The plugin is active and handling voucher data
  3. Locate gift voucher input functionality
    Navigate to the plugin admin area or frontend voucher creation form where users can input voucher data such as recipient name, message, or custom fields
    Affected if User-supplied input fields exist that accept freeform text for vouchers
  4. Inspect voucher output rendering
    View the source code or HTML output of a published voucher page and check if voucher field values are wrapped in appropriate escaping functions (esc_html, esc_attr, esc_textarea) or output directly without escaping
    Affected if Voucher field values appear in HTML output without proper escaping functions like esc_html or esc_attr
  5. Check database storage of voucher data
    Query the wp_posts or custom tables where voucher data is stored and inspect stored values for any raw HTML or script tags that may have been saved without sanitization
    Affected if Voucher data in the database contains unescaped or unsanitized user input including potential malicious scripts

A user is affected if the Codemenschen Gift Vuzzers plugin is installed, active, and voucher field data is rendered on pages without proper escaping functions like esc_html or esc_attr.

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

Implement proper input sanitization on all user-supplied voucher fields using WordPress sanitization functions (such as sanitize_text_field, esc_attr, or esc_html) and ensure all output is encoded with appropriate escaping functions before rendering.

Recommended fix Moderate confidence

Latest available version of Codemenschen Gift Vouchers plugin (version > 4.7.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Gift Vouchers' plugin by Codemenschen
  4. 4. Check if the currently installed version is 4.7.0 or lower
  5. 5. If vulnerable, click 'Update Now' to install the latest version, or manually download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After update, verify the plugin is functioning correctly on the frontend

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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