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

> Unauthenticated attackers can exploit CSRF to inject stored XSS payloads into the admin panel, potentially leading to administrator account takeover.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-p637-7ww8-j45c

## What is CVE-2026-6395?

CVE-2026-6395 is a medium-severity vulnerability in winking Word 2 Cash, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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 <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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-6395?


## How do I fix CVE-2026-6395?

No fix has been published for CVE-2026-6395 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6395 being exploited?

There is no known exploitation of CVE-2026-6395 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6395 and fix it if it is affected.

What it is: CVE-2026-6395 is a medium-severity vulnerability in winking Word 2 Cash, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6395 in the wild and no public exploit code.

Affected product: winking Word 2 Cash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6395/ (Markdown: https://insights.sbomify.com/CVE-2026-6395/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6395
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6395
- OSV: https://osv.dev/vulnerability/CVE-2026-6395

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6395/
Summaries are generated and may contain mistakes; the official description above is the record.