CVE-2026-6395: Word 2 Cash <= 0.9.2 - Cross-Site Request Forgeryto Stored Cross-Site Scripting via Settings Page

Published May 20, 2026
·
Updated

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.

Affected Software

1 affected component
Word 2 Cash<=0.9.2

Event History

May 20, 2026
CVE Published
via MITRE·01:25 AM
Data Sourced
via MITRE·01:25 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-6395?

CVE-2026-6395 is classified as a high severity vulnerability due to its potential for Cross-Site Request Forgery leading to Stored Cross-Site Scripting.

2

How do I fix CVE-2026-6395?

To fix CVE-2026-6395, update the Word 2 Cash plugin to version 0.9.3 or later where the vulnerability is addressed.

3

Who is affected by CVE-2026-6395?

CVE-2026-6395 impacts users of the Word 2 Cash plugin for WordPress in versions up to and including 0.9.2.

4

What types of attacks does CVE-2026-6395 facilitate?

CVE-2026-6395 facilitates Cross-Site Request Forgery attacks that can result in Stored Cross-Site Scripting on affected sites.

5

Is CVE-2026-6395 already exploited in the wild?

As of the latest information, there are no confirmed reports of CVE-2026-6395 being actively exploited in the wild.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203