dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12432

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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 WP Full Stripe Free plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 8.4.3 via the wpfs_update_failed_payment_status AJAX action. The handler is registered through both wp_ajax_ and wp_ajax_nopriv_ hooks and the underlying update_failed_payment_status() function performs no capability check, no nonce verification, and no logged-in check before calling $this->db->updatePaymentByEventId() with attacker-controlled POST parameters. This makes it possible for unauthenticated attackers who can obtain a valid Stripe Payment Intent ID for the target site (Payment Intent IDs are exposed to the customer browser during normal Stripe.js checkout flows) to manipulate payment records in the site's database, marking previously successful payments as failed and overwriting failure codes and messages with attacker-supplied values.

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 WP Full Stripe Free plugin for WordPress (versions up to 8.4.3) has a missing authorization vulnerability in the wpfs_update_failed_payment_status AJAX action. This action is registered with both wp_ajax_ and wp_ajax_nopriv_ hooks, allowing unauthenticated access. The update_failed_payment_status() function performs no capability check, nonce verification, or logged-in user validation before updating payment records via $this->db->updatePaymentByEventId() using attacker-controlled POST parameters. This enables unauthenticated attackers with a valid Stripe Payment Intent ID to manipulate payment records, marking successful payments as failed and overwriting failure codes/messages.

MitigationAdd proper authorization checks (current_user_can), nonce verification (check_ajax_referer), and remove the AJAX action from wp_ajax_nopriv_ hook to restrict access to authenticated users only.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Identify if WP Full Stripe Free plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Full Stripe Free' or check the plugin files in /wp-content/plugins/ for a folder containing 'full-stripe'
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    Check the plugin main file header in /wp-content/plugins/full-stripe/free-stripe.php (or similar path) for the 'Version' comment, or view the plugin details in WordPress admin plugins list
    Affected if The version is 8.4.3 or below (any version up to and including 8.4.3)
  3. Locate the vulnerable AJAX action registration
    Search plugin PHP files for 'wpfs_update_failed_payment_status' or 'wp_ajax_wpfs_update_failed_payment_status' to find where the AJAX action is registered
    Affected if This AJAX action exists in the plugin codebase
  4. Check if the AJAX action allows unauthenticated access
    Search for the add_action calls registering this action - look for 'wp_ajax_nopriv_wpfs_update_failed_payment_status' which enables unauthenticated access
    Affected if The action is registered with wp_ajax_nopriv_ hook (allowing unauthenticated users)
  5. Verify missing authorization in the callback function
    Find the update_failed_payment_status() function and check for absence of current_user_can(), check_ajax_referer(), and logged-in user validation before processing POST data
    Affected if The function performs no capability checks, nonce verification, or user authentication validation before updating payment records

A user is affected if the WP Full Stripe Free plugin (versions up to 8.4.3) is installed with the vulnerable AJAX action registered for unauthenticated access and lacking authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add proper authorization checks (current_user_can), nonce verification (check_ajax_referer), and remove the AJAX action from wp_ajax_nopriv_ hook to restrict access to authenticated users only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12432 — 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-2026-12432 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