InfusedWoo Pro <= 5.1.2 - Unauthenticated Arbitrary File Read via 'url' Parameter
Strategic Overview
- Status
- Patched in 5.1.3
- Affected Plugin
- InfusedWoo Pro
- Affected Version
<= 5.1.2- CVSS
- 7.5High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-6514
At a glance
CVE-2026-6514 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the InfusedWoo Pro WordPress plugin, affecting versions <= 5.1.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality 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 Arbitrary File Read in all versions up to, and including, 5.1.2 via the popup_submit. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in InfusedWoo Pro <= 5.1.2 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. 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?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: InfusedWoo Pro 5.1.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C