dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-1648

HIGH · 7.2 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Performance Monitor WordPress plugin has an unauthenticated SSRF vulnerability in the REST API endpoint /wp-json/performance-monitor/v1/curl_data due to insufficient validation of the 'url' parameter. Attackers can abuse this to make arbitrary web requests including to internal services via dangerous protocols like Gopher, potentially achieving RCE through service chaining with Redis.

MitigationUpdate to a patched version of the plugin once available, or disable/remove the plugin until a fix is released. If the plugin is required, implement strict allowlist validation for the url parameter to restrict which destinations can be requested.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Performance Monitor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Performance Monitor', or check the /wp-content/plugins/ directory for a performance-monitor folder. Check plugin version in plugin details.
    Affected if Plugin is installed and active with version you cannot confirm is patched
  2. Confirm the vulnerable REST API endpoint exists
    Send a GET request to /wp-json/performance-monitor/v1/curl_data - if it responds (even with an error), the endpoint is registered and the plugin is vulnerable if the url parameter lacks proper validation.
    Affected if Endpoint returns any valid JSON response indicating it exists
  3. Test SSRF vulnerability with a benign internal request
    Send a POST request to /wp-json/performance-monitor/v1/curl_data with a url parameter pointing to an internal address (e.g., http://127.0.0.1:port or http://localhost) or a known internal service. Check if the response reveals the plugin made the request.
    Affected if Plugin accepts and processes arbitrary URLs including internal localhost/internal network addresses
  4. Check if dangerous protocols are accepted
    Send a POST request with url parameter set to a Gopher protocol URL (e.g., gopher://127.0.0.1:6379/_). If the plugin does not reject this, the SSRF is exploitable with dangerous protocols.
    Affected if Plugin accepts gopher:// or other dangerous protocols without rejection

A user is affected if the Performance Monitor plugin is installed and the /wp-json/performance-monitor/v1/curl_data endpoint accepts arbitrary URLs including internal addresses or dangerous protocols like Gopher.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the plugin once available, or disable/remove the plugin until a fix is released. If the plugin is required, implement strict allowlist validation for the url parameter to restrict which destinations can be requested.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1648 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data