SureForms <= 1.13.1 - Cross-Site Request Forgery Protection Bypass via Improper Nonce Distribution
Strategic Overview
- Status
- Patched in 1.13.2
- Affected Version
<= 1.13.1- CVSS
- 5.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-12535
At a glance
CVE-2025-12535 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the SureForms WordPress plugin, affecting versions <= 1.13.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.13.2; sites on affected versions should update now. Disclosed November 2025, reported by type5afe.
Vulnerability Overview
The SureForms plugin for WordPress is vulnerable to Cross-Site Request Forgery Bypass in all versions up to, and including, 1.13.1. This is due to the plugin distributing generic WordPress REST API nonces (wp_rest) to unauthenticated users via the 'wp_ajax_nopriv_rest-nonce' action. While the plugin legitimately needs to support unauthenticated form submissions, it incorrectly uses generic REST nonces instead of form-specific nonces. This makes it possible for unauthenticated attackers to bypass CSRF protection on REST API endpoints that rely solely on nonce verification without additional authentication checks, allowing them to trigger unauthorized actions such as the plugin's own post-submission hooks and potentially other plugins' REST endpoints.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
SureForms <= 1.13.1 carries this weakness at wp_ajax_nopriv_rest-nonce, and reaching it 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 SureForms the fix is 1.13.2: builds <= 1.13.1 are affected, anything from 1.13.2 onward is not.
Remediation
Update to version 1.13.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to SureForms: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SureForms 1.13.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in SureForms – Contact Form Builder, AI Forms, Payment Form, Survey & Quiz
- 8.1CVE-2025-6691: SureForms Arbitrary File Deletion Triggered
CVE-2025-6691 - 7.5CVE-2026-4987: SureForms <= 2.5.2 Payment Amount Validation Bypass
CVE-2026-4987 - 7.5CVE-2026-15288: SureForms Stripe Payment Amount Manipulation
CVE-2026-15288 - 7.5CVE-2025-6742: SureForms PHP Object Injection (PHAR) Triggered
CVE-2025-6742 - 7.2CVE-2026-18406: SureForms <= 2.12.2 Stored Cross-Site Scripting
CVE-2026-18406 - 7.2CVE-2025-14855: SureForms <= 2.2.0 Stored Cross-Site Scripting
CVE-2025-14855 - 6.4CVE-2026-7623: SureForms <= 2.8.1 Stored Cross-Site Scripting
CVE-2026-7623 - 6.1CVE-2025-5921: SureForms <= 1.7.1 Reflected Cross-Site Scripting
CVE-2025-5921
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C