InfusedWoo Pro <= 5.1.2 - Unauthenticated Missing Authorization to Arbitrary Post Deletion via Multiple Parameters
Strategic Overview
- Status
- Patched in 5.1.3
- Affected Plugin
- InfusedWoo Pro
- Affected Version
<= 5.1.2- CVSS
- 9.1Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-6512
At a glance
CVE-2026-6512 is a critical-severity Missing Authorization vulnerability in the InfusedWoo Pro WordPress plugin, affecting versions <= 5.1.2. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 5.1.3; sites on affected versions should update now. Disclosed May 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).
Vulnerability Overview
The InfusedWoo Pro plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.1.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to permanently delete arbitrary posts, pages, products, or orders, mass-delete all comments on any post, and change any post's status.
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. A successful exploit has high impact on confidentiality, integrity.
CWE-862: Missing Authorization
Reaching this weakness in InfusedWoo Pro <= 5.1.2 takes no account at all. 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 InfusedWoo Pro the fix is 5.1.3: builds <= 5.1.2 are affected, anything from 5.1.3 onward is not.
Remediation
Update to version 5.1.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: InfusedWoo Pro 5.1.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in InfusedWoo Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C