CVE-2026-6395 MEDIUM

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

Vendor Winking
Product Word 2 Cash
Weakness CWE-352 · CSRF
Published May 20, 2026
Last update May 20, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Word 2 Cash versions 0.9.2 and earlier are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without the administrator's knowledge or consent. The attack requires the victim to visit the attacker's page while authenticated.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings, create accounts, or change content if an admin visits a malicious link while logged in.

Conditions required to exploit

05Prerequisites

Site admin must be logged in and visit an attacker-controlled webpage; no special privileges required.

Key dates

06Disclosure timeline

May 20, 2026 CVE published
May 20, 2026 Record updated