Plugins · performance-monitor · data as of 2026-11-04
Is Performance Monitor safe? Known vulnerabilities and latest version
- Status
- Closed 2026-03-05
- Known issues on record
- 2
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate performance-monitor && wp plugin delete performance-monitor
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.
medium 5.8 CVE-2026-3881 · published 2026-03-31
Server-side request forgery (SSRF) in Performance Monitor (1.0.6 and older)
- Affected
- 1.0.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Performance Monitor WordPress plugin through 1.0.6 does not validate a parameter before making a request to it, which could allow unauthenticated users to perform SSRF attacks
high 7.2 CVE-2026-1648 · published 2026-03-21
Remote code execution in Performance Monitor (1.0.6 and older)
- Affected
- 1.0.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Performance Monitor plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0.6. This is due to insufficient validation of the 'url' parameter in the '/wp-json/performance-monitor/v1/curl_data' REST API endpoint. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations, including internal services, via the Gopher protocol and other dangerous protocols. This can be exploited to achieve Remote Code Execution by chaining with services like Redis.
Recent activity
- 2026-03-05 — closed on wordpress.org (Security Issue).
- 2026-03-31 — Server-side request forgery (SSRF) disclosed (CVE-2026-3881), fix version not stated.
- 2026-03-21 — Remote code execution disclosed (CVE-2026-1648), fix version not stated.
Get an email when Performance Monitor has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Performance Monitor (performance-monitor) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Server-side request forgery (SSRF) (1) · Remote code execution (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/performance-monitor (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/performance-monitor"><img src="https://laskyr.com/plugins/performance-monitor/badge.svg" alt="Performance Monitor vulnerability status"></a>