Loading vulnerability…
CVE-2026-12432 affects the WP Full Stripe Free WordPress plugin in versions up to and including 8.4.3. The vulnerability is in the wpfs_update_failed_payment_status AJAX action, which is exposed through both the authenticated wp_ajax_ hook and the unauthenticated wp_ajax_nopriv_ hook. The underlying update_failed_payment_status() handler does not perform a capability check, nonce verification, or logged-in check before invoking $this->db->updatePaymentByEventId() with attacker-controlled POST parameters. As a result, an unauthenticated attacker who knows a valid Stripe Payment Intent ID associated with the target site can submit crafted requests that alter payment records in the WordPress site's database, including changing previously successful payments to failed and replacing stored failure codes and messages with attacker-supplied values.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.