Summary
The Performance Monitor plugin for WordPress up to version 1.0.6 fails to sanitize the url parameter in its /wp-json/performance-monitor/v1/curl_data endpoint, allowing arbitrary outbound requests.
An unauthenticated attacker can coerce the server to contact internal or protocol-specific targets, enabling data exfiltration or remote code execution when chained with services such as Redis.
Affected context
The vulnerability manifests when:
- The Performance Monitor plugin (≤1.0.6) is active on a WordPress site.
- The REST API endpoint
/wp-json/performance-monitor/v1/curl_datais exposed to unauthenticated users. - URL inputs are forwarded to curl without scheme, host, or protocol restrictions.
It becomes most dangerous in environments where the WordPress host can reach internal control-plane services or speaks protocols like Gopher.
Exploit preconditions
- Attack surface: Public WordPress REST API.
- Required access: None; endpoint is callable without authentication.
- Trigger point: Submission of a crafted
urlparameter to/wp-json/performance-monitor/v1/curl_data. - Why exploitation is possible: Curl invocation trusts user-supplied URLs and permits arbitrary schemes, enabling pivoting into internal networks or protocol abuse.
Why this happens
The plugin forwards user-controlled URLs directly into server-side HTTP requests, lacking scheme allowlists, host validation, or metadata controls.
This embodies CWE-918 where server-side fetches of untrusted URLs permit interaction with protected resources or dangerous protocols.
Potential impact
- Internal service probing or metadata exposure.
- Command execution through protocol gadgets (e.g., Gopher to Redis).
- Data exfiltration from services inaccessible to the public Internet.
- Facilitation of lateral movement within the hosting network.
General mitigation guidance
- Constrain outbound requests to vetted schemes (https/http) and apply host/IP allowlists.
- Introduce proxy layers or metadata services that enforce protocol, port, and network segment policies.
- Sanitize and canonicalize user input before invoking server-side fetches.
- Run application processes with minimized network reach to sensitive back-ends and disallow protocol handlers unnecessary for plugin functionality.
How teams detect issues like this
- Static review for direct use of curl or HTTP clients with user-supplied URLs lacking validation.
- Automated scanning for REST endpoints that echo or fetch arbitrary URLs.
- Network monitoring to flag unusual outbound protocols (e.g., Gopher) originating from WordPress hosts.
- Policy-as-code checks ensuring URL parameters pass through validation or allowlist utilities.

