qrolic Performance Monitor Plugin up to 1.0.6 on WordPress REST API Endpoint curl_data url server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in qrolic Performance Monitor Plugin up to 1.0.6 on WordPress. This affects an unknown part of the file /wp-json/performance-monitor/v1/curl_data of the component REST API Endpoint. Executing a manipulation of the argument url can lead to server-side request forgery. This vulnerability is handled as CVE-2026-1648. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in qrolic Performance Monitor Plugin up to 1.0.6 on WordPress and classified as critical. This vulnerability affects an unknown function of the file /wp-json/performance-monitor/v1/curl_data of the component REST API Endpoint. The manipulation of the argument url with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was released by Afshin Shekaari. The advisory is shared for download at wordfence.com. This vulnerability was named CVE-2026-1648 since 01/29/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
Upgrading to version 1.0.6 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.2
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Performance Monitor Plugin 1.0.6
Timeline
01/29/2026 CVE reserved03/21/2026 Advisory disclosed
03/21/2026 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Afshin Shekaari
Status: Confirmed
CVE: CVE-2026-1648 (🔒)
GCVE (CVE): GCVE-0-2026-1648
GCVE (VulDB): GCVE-100-352156
Entry
Created: 03/21/2026 06:36Updated: 03/27/2026 13:01
Changes: 03/21/2026 06:36 (69), 03/27/2026 13:01 (1)
Complete: 🔍
Cache ID: 216:575:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.