dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-6395

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-20
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 Word 2 Cash plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in versions up to and including 0.9.2. This is due to the complete absence of nonce verification on the settings save handler in the w2c_admin() function, combined with missing input sanitization before storage and missing output escaping when rendering the stored value. The w2c-definitions POST parameter is saved raw via update_option() and later echoed without escaping inside a <textarea> element. This makes it possible for unauthenticated attackers to forge a request on behalf of a logged-in administrator, storing arbitrary JavaScript payloads that execute in the WordPress admin panel whenever the settings page is visited.

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 Word 2 Cash plugin versions 0.9.2 and below lack CSRF protection (no nonce verification) on its settings save handler, and fail to sanitize the w2c-definitions parameter before storage and escape it during output. This allows unauthenticated attackers to forge requests on behalf of administrators to inject malicious JavaScript that executes in the admin panel.

MitigationAdd nonce verification to the settings save handler, implement input sanitization via sanitize_text_field() or equivalent before update_option(), and escape output with htmlspecialchars() or esc_textarea() before echoing in the textarea.

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. Verify WordPress is installed
    Check for wp-config.php in the document root or access the site health page at /wp-admin/site-health.php
    Affected if WordPress is not present, this CVE does not apply
  2. Confirm Word 2 Cash plugin is installed
    Check the plugins directory (wp-content/plugins/) for a folder named 'word-2-cash' or 'word2cash', or look for it in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is not installed, this CVE does not apply
  3. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Word 2 Cash. Compare the version number to the affected range (0.9.2 and below). Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if Version is 0.9.2 or lower - the environment is potentially affected
  4. Inspect the w2c-definitions database option
    Access the WordPress database (via phpMyAdmin or wp-cli) and query: SELECT * FROM wp_options WHERE option_name = 'w2c-definitions'; (note: prefix may vary if custom table prefix is used)
    Affected if The option value contains unsanitized script tags or unexpected HTML that was injected via the vulnerable parameter
  5. Check if the settings page is accessible
    Navigate to the plugin's admin settings page (typically /wp-admin/admin.php?page=word-2-cash or similar) and locate the w2c-definitions textarea field. View the page source to see if the value is rendered without escaping (look for raw script tags or unescaped quotes in the HTML)
    Affected if The w2c-definitions value is echoed inside a textarea without esc_textarea() escaping, allowing stored XSS execution

A user is affected if they have Word 2 Cash plugin version 0.9.2 or lower installed, and the w2c-definitions option in the database contains injected JavaScript or the settings page renders this value without proper escaping.

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

Add nonce verification to the settings save handler, implement input sanitization via sanitize_text_field() or equivalent before update_option(), and escape output with htmlspecialchars() or esc_textarea() before echoing in the textarea.

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-6395 — 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-6395 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