ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-1648

The Performance Monitor plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0.6.

Published Mar 21, 2026 · catalog updated Jun 17, 2026 · The Performance Monitor plugin

Check if you run it

No confirmed exploitation is on record for CVE-2026-1648. EPSS is 0.37%. Act only if a listed version of The Performance Monitor plugin is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Performance Monitor plugin).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.37%
Remediation
Version ranges on file
Affected products
stated named in the record

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 1.0.6

How to fix CVE-2026-1648

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-1648. EPSS is 0.37%. Act only if a listed version of The Performance Monitor plugin is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 1.0.6. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 21, 2026 · NIST NVD

    Detected

    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 th

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 th

Sources

  • CVE.orgVulnerability recordCVE-2026-1648

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-1648

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-1648

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.