WordPress security changelog
MEDIUM CVE-2026-6395 Deferred

Word 2 Cash: Cross-site scripting

Word 2 Cash is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 0.9.2.

CVE / CNA score 6.1 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Word 2 Cash
Plugin slug
word-2-cash
Affected
<= 0.9.2
Safe version
> 0.9.2
Published
May 20, 2026
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published May 20, 2026 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Word 2 Cash to a release after 0.9.2, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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