dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9322

HIGH · 7.5 CVSS v3.1 Published 2025-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Stripe Payment Forms by WP Full Pay WordPress plugin versions up to 8.3.1 contains an unauthenticated SQL injection vulnerability in the 'wpfs-form-name' parameter. Attackers can inject malicious SQL queries due to insufficient input sanitization and lack of prepared statements in the underlying SQL query, potentially allowing complete database compromise.

MitigationUpdate the plugin to version 8.3.2 or later. If immediate updating is not possible, consider disabling the plugin until a patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Locate the Stripe Payment Forms by WP Full Pay plugin in your WordPress installation under wp-content/plugins/ or via WordPress admin dashboard > Plugins
    Affected if Plugin is not installed or has been removed entirely
  2. Identify installed version
    Check the plugin version number in WordPress admin > Plugins > Stripe Payment Forms by WP Full Pay, or read the main plugin file header for the 'Version' field
    Affected if Installed version is 8.3.1 or any version below 8.3.2 (e.g., 8.3.0, 8.2.9, etc.)
  3. Verify plugin is active
    Confirm the plugin status in WordPress admin > Plugins shows the plugin as 'Active'
    Affected if Plugin is active and version is 8.3.1 or below - this is the vulnerable state
  4. Confirm vulnerable parameter exposure
    Identify forms or endpoints that accept the 'wpfs-form-name' parameter - this is typically submitted with payment forms. Check your website exposes any public-facing payment forms using this plugin.
    Affected if Public payment forms accepting wpfs-form-name parameter are in use on an unpatched version

Your environment is affected if the Stripe Payment Forms by WP Full Pay plugin is installed, active, and running version 8.3.1 or below, with public payment forms that submit the wpfs-form-name parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 8.3.2 or later. If immediate updating is not possible, consider disabling the plugin until a patch can be applied.

Recommended fix Moderate confidence

Stripe Payment Forms by WP Full Pay version 8.3.2 or latest release

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Update the 'Stripe Payment Forms by WP Full Pay' plugin to the latest available version from the WordPress plugin repository.
  3. 3. After updating, verify the plugin is running version 8.3.2 or later.
  4. 4. Test that payment forms still function correctly after the update.
  5. 5. Monitor plugin logs and site for any unusual database activity.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9322 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data