CVE-2025-9322

Stripe Payment Forms <= 8.3.1 - Unauthenticated SQL Injection

2025-10-24 18:16
mikemyers

Strategic Overview

Status
Patched in 8.3.2
Affected Plugin
Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions
Affected Version
<= 8.3.1
CVSS
7.5High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2025-9322
View all Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions vulnerabilities

At a glance

CVE-2025-9322 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Stripe Payment Forms by WP Full Pay WordPress plugin, affecting versions <= 8.3.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 8.3.2; sites on affected versions should update now. Disclosed October 2025, reported by mikemyers.

Vulnerability Overview

The Stripe Payment Forms by WP Full Pay – Accept Credit Card Payments, Donations & Subscriptions plugin for WordPress is vulnerable to SQL Injection via the 'wpfs-form-name' parameter in all versions up to, and including, 8.3.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Stripe Payment Forms by WP Full Pay <= 8.3.1 carries this weakness at wpfs-form-name, and reaching it takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Stripe Payment Forms by WP Full Pay the fix is 8.3.2: builds <= 8.3.1 are affected, anything from 8.3.2 onward is not.

Remediation

Update to version 8.3.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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 8.3.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-9322https://www.wordfence.com/threat-intel/vulnerabilities/id/886b612a-d0d1-4880-b423-eb62410a28cdhttps://nvd.nist.gov/vuln/detail/CVE-2025-9322

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C