WP Full Stripe Free <= 7.0.17 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 7.0.18
- Affected Plugin
- Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
- Affected Version
<= 7.0.17- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-47667
At a glance
CVE-2023-47667 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stripe Payment Forms by WP Full Pay WordPress plugin, affecting versions <= 7.0.17. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.0.18; sites on affected versions should update now. Disclosed November 2023, reported by LEE SE HYOUNG.
Vulnerability Overview
The WP Full Stripe Free plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 7.0.17. This is due to missing or incorrect nonce validation via several functions in the ~/include/wp-full-stripe-admin-menu.php file. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Stripe Payment Forms by WP Full Pay <= 7.0.17 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Stripe Payment Forms by WP Full Pay the fix is 7.0.18: builds <= 7.0.17 are affected, anything from 7.0.18 onward is not.
Remediation
Update to version 7.0.18, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Stripe Payment Forms by WP Full Pay: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Stripe Payment Forms by WP Full Pay 7.0.18 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
- 7.5CVE-2025-9322: Stripe Payment Forms <= 8.3.1 SQL Injection
CVE-2025-9322 - 7.2CVE-2026-61960: Stripe Payment Forms by WP Full Pay Stored XSS
CVE-2026-61960 - 5.3CVE-2026-80311: Stripe Payment Forms by WP Full Pay IDOR
CVE-2026-80311 - 5.3CVE-2026-77758: Stripe Payment Forms by WP… Information Exposure
CVE-2026-77758 - 5.3CVE-2026-77789: Stripe Payment Forms by WP Full Pay IDOR
CVE-2026-77789 - 5.3CVE-2026-16734: Stripe Payment Forms by WP… Missing Authorization
CVE-2026-16734 - 5.3CVE-2026-12432: Stripe Payment Forms by WP… Unauthenticated Payment
CVE-2026-12432 - 4.9CVE-2025-58789: WP Full Stripe Free <= 8.2.5 SQL Injection
CVE-2025-58789
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C