Ninja Forms - Save Progress <= 3.0.30 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Data Deletion via admin-ajax.php with admin_init Hook
Strategic Overview
- Status
- Patched in 3.0.31
- Affected Plugin
- Ninja Forms - Save Progress
- Affected Version
<= 3.0.30- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-15550
At a glance
CVE-2026-15550 is a medium-severity Missing Authorization vulnerability in the Ninja Forms - Save Progress WordPress plugin, affecting versions <= 3.0.30. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.0.31; sites on affected versions should update now. Disclosed September 2026, reported by Hermione.
Vulnerability Overview
The Ninja Forms - Save Progress plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 3.0.30. This is due to the lack of capability checks and nonce verification in the 'bulk_actions' function. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary database records from the 'wp_nf3_objects' table, such as saved submissions.
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 interaction from a victim user.
CWE-862: Missing Authorization
Ninja Forms - Save Progress <= 3.0.30 carries this weakness at bulk_actions, and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Ninja Forms - Save Progress the fix is 3.0.31: builds <= 3.0.30 are affected, anything from 3.0.31 onward is not.
Remediation
Update to version 3.0.31, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Ninja Forms - Save Progress 3.0.31 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C