CVE-2026-1648: CWE-918 Server-Side Request Forgery (SSRF) in qrolic Performance Monitor
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.
AI Analysis
Technical Summary
The qrolic Performance Monitor plugin for WordPress contains an SSRF vulnerability (CWE-918) due to improper validation of the 'url' parameter in its REST API endpoint '/wp-json/performance-monitor/v1/curl_data'. This allows unauthenticated attackers to induce the server to make arbitrary requests to internal or external resources, including via the Gopher protocol. Exploitation can lead to Remote Code Execution by leveraging vulnerable services like Redis. The vulnerability affects all versions up to and including 1.0.6 and has a CVSS 3.1 base score of 7.2 (High). No patch or remediation details are currently provided by the vendor.
Potential Impact
An unauthenticated attacker can exploit this SSRF vulnerability to make arbitrary requests from the server, potentially accessing internal services that are not otherwise exposed. By chaining this SSRF with other vulnerable services such as Redis, an attacker may achieve Remote Code Execution. This could lead to unauthorized access, data exposure, or control over the affected system. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the vulnerable REST API endpoint if possible, and monitor for unusual internal requests originating from the server. Avoid exposing internal services that could be leveraged in exploitation chains. Do not rely on generic mitigations unless specifically recommended by the vendor.
CVE-2026-1648: CWE-918 Server-Side Request Forgery (SSRF) in qrolic Performance Monitor
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The qrolic Performance Monitor plugin for WordPress contains an SSRF vulnerability (CWE-918) due to improper validation of the 'url' parameter in its REST API endpoint '/wp-json/performance-monitor/v1/curl_data'. This allows unauthenticated attackers to induce the server to make arbitrary requests to internal or external resources, including via the Gopher protocol. Exploitation can lead to Remote Code Execution by leveraging vulnerable services like Redis. The vulnerability affects all versions up to and including 1.0.6 and has a CVSS 3.1 base score of 7.2 (High). No patch or remediation details are currently provided by the vendor.
Potential Impact
An unauthenticated attacker can exploit this SSRF vulnerability to make arbitrary requests from the server, potentially accessing internal services that are not otherwise exposed. By chaining this SSRF with other vulnerable services such as Redis, an attacker may achieve Remote Code Execution. This could lead to unauthorized access, data exposure, or control over the affected system. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the vulnerable REST API endpoint if possible, and monitor for unusual internal requests originating from the server. Avoid exposing internal services that could be leveraged in exploitation chains. Do not rely on generic mitigations unless specifically recommended by the vendor.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-29T19:03:40.942Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69be1807f4197a8e3b783c43
Added to database: 3/21/2026, 4:01:11 AM
Last enriched: 4/9/2026, 11:20:57 AM
Last updated: 5/3/2026, 7:55:20 PM
Views: 125
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.