PhastPress <= 3.10 - Unauthenticated Server-Side Request Forgery via 'src' Parameter
Strategic Overview
- Status
- Patched in 3.11
- Affected Plugin
- PhastPress
- Affected Version
<= 3.10- CVSS
- 7.3High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-3712
At a glance
CVE-2026-3712 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the PhastPress WordPress plugin, affecting versions <= 3.10. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.11; sites on affected versions should update now. Disclosed October 2026, reported by Itthidej Aramsri (Boeing777).
Vulnerability Overview
The PhastPress plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.10 This is due to the scripts service endpoint constructing its URL whitelist dynamically from the attacker-controlled HTTP 'Host' header. This makes it possible for unauthenticated attackers to spoof the header to match any target URL, bypassing the whitelist and forcing the server to make HTTP requests to arbitrary internal or external destinations and return the response content.
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-918: Server-Side Request Forgery (SSRF)
PhastPress <= 3.10 carries this weakness at Host, and reaching it 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 PhastPress the fix is 3.11: builds <= 3.10 are affected, anything from 3.11 onward is not.
Remediation
Update to version 3.11, 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: PhastPress 3.11 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in PhastPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C