InfusedWoo Pro <= 5.1.18 - Authenticated (Subscriber+) Privilege Escalation via Password Reset Link Disclosure
Strategic Overview
- Status
- Patched in 5.1.18
- Affected Plugin
- InfusedWoo Pro
- Affected Version
<= 5.1.17- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-19892
At a glance
CVE-2026-19892 is a high-severity Missing Authorization vulnerability in the InfusedWoo Pro WordPress plugin, affecting versions <= 5.1.17. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.1.18; sites on affected versions should update now. Disclosed August 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).
Vulnerability Overview
The InfusedWoo Pro plugin for WordPress is vulnerable to Privilege Escalation via Account Takeover in all versions up to, and including, 5.1.17. This is due to a missing capability check in the `ajax_iwar_preview_email()` function, which uses `is_admin()` as its only authorization check and allows low-privilege users to render email preview merge fields for an arbitrary email address. This makes it possible for authenticated attackers, with subscriber-level access and above, to generate and retrieve a valid password reset link for any WordPress user, including administrators, enabling account takeover.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
InfusedWoo Pro <= 5.1.17 carries this weakness at ajax_iwar_preview_email(), 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 InfusedWoo Pro the fix is 5.1.18: builds <= 5.1.17 are affected, anything from 5.1.18 onward is not.
Remediation
Update to version 5.1.18, 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: InfusedWoo Pro 5.1.18 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