# CVE-2026-96574: WordPress User Frontend plugin stored XSS in payment method

Source: https://junglewise.ai/threats/cve-2026-96574-the-user-frontend-membership-user-registration-user-profile-user  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-10. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-96574 · Severity: medium · CVSS 6.4 · Published 2026-10-10

The User Frontend plugin for WordPress allows users to manage registrations, profiles, and submit content via a web interface. An authenticated attacker with subscriber-level access can inject malicious JavaScript through the payment method parameter that executes for all site visitors, enabling account takeover, credential theft, or malware distribution.

Vendors: [WP User Frontend](https://junglewise.ai/threats/vendors/wp-user-frontend).

## Quick answers

**Is CVE-2026-96574 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-96574 being exploited in the wild.

**How severe is CVE-2026-96574?** Medium severity, with a CVSS score of 6.4, published 10 October 2026.

**Which products and versions are affected?** WP User Frontend User Frontend up to 4.3.12.

**Is there a fix for CVE-2026-96574?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-96574 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-96574?** Check whether you run WP User Frontend User Frontend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

Stored cross-site scripting (XSS) vulnerability in the 'wpuf_payment_method' parameter due to incomplete input sanitization and missing output escaping. The vulnerability exploits a bypass technique where appending a valid gateway keyword (e.g., 'bank') to an HTML payload allows the malicious script to be stored and later rendered unescaped, while the sanitizer only processes the keyword. Requires authenticated access at subscriber level or higher.

## Affected products

- WP User Frontend User Frontend up to 4.3.12

## Timeline

- 2026-10-10: disclosed

## References

- [https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.12/Lib/Gateway/Bank.php](https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.12/Lib/Gateway/Bank.php)
- [https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.12/includes/Admin/List_Table_Transactions.php](https://plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.12/includes/Admin/List_Table_Transactions.php)