WordPress security changelog
HIGH CVE-2026-3712 Deferred

PhastPress: Server-side request forgery

PhastPress constructs the scripts-service URL allowlist from the attacker-controlled HTTP Host header. An unauthenticated caller can spoof that header to match a target URL, bypass the allowlist and cause the server to request arbitrary internal or external HTTP destinations and return their response content. The export does not identify the full service route or destination-URL parameter. Published affected versions: <= 3.10.

CVE / CNA score 7.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
PhastPress
Plugin slug
phastpress
Affected
<= 3.10
Safe version
See mitigation notes
Published
Oct 15, 2026
Weakness
CWE-918 — Server-Side Request Forgery (SSRF)

This CVE was published Oct 15, 2026 and is one of 3 known issues for this plugin.

Update, patch or deactivate.

Official author release notes reviewed on 2026-10-15 list version 3.12, but this archive could not confirm a fixed version for this CVE. Script, CDN and proxy compatibility changes do not establish Host-header SSRF remediation. This is an evidence limitation, not a claim that the current release remains vulnerable. Official release notes: https://wordpress.org/plugins/phastpress/#developers. Restrict the affected scripts service and use a server-controlled destination allowlist rather than the request Host header. Assess whether internal services or sensitive response data were exposed.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Primary and upstream sources