CVE-2026-3881 | Performance Monitor Plugin up to 1.0.6 on WordPress server-side request forgery
VulDBArchived Mar 31, 2026✓ Full text saved
A vulnerability has been found in Performance Monitor Plugin up to 1.0.6 on WordPress and classified as critical . This affects an unknown function. The manipulation leads to server-side request forgery. This vulnerability is traded as CVE-2026-3881 . It is possible to initiate the attack remotely. There is no exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354330 · CVE-2026-3881 · GCVE-0-2026-3881
PERFORMANCE MONITOR PLUGIN UP TO 1.0.6 ON WORDPRESS SERVER-SIDE REQUEST FORGERY
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.1 $0-$5k 2.30+
Summaryinfo
A vulnerability was found in Performance Monitor Plugin up to 1.0.6 on WordPress and classified as critical. This impacts an unknown function. The manipulation results in server-side request forgery. This vulnerability is known as CVE-2026-3881. It is possible to launch the attack remotely. No exploit is available.
Detailsinfo
A vulnerability classified as critical has been found in Performance Monitor Plugin up to 1.0.6 on WordPress. Affected is an unknown code. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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
The weakness was published by Afshin Shekaari. The advisory is available at wpscan.com. This vulnerability is traded as CVE-2026-3881 since 03/10/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 03/31/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Type
WordPress Plugin
Name
Performance Monitor Plugin
Version
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
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: 🔍
Exploitinginfo
Class: Server-side request forgery
CWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/10/2026 CVE reserved
03/31/2026 +20 days Advisory disclosed
03/31/2026 +0 days VulDB entry created
03/31/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: wpscan.com
Researcher: Afshin Shekaari
Status: Not defined
CVE: CVE-2026-3881 (🔒)
GCVE (CVE): GCVE-0-2026-3881
GCVE (VulDB): GCVE-100-354330
Entryinfo
Created: 03/31/2026 08:58
Changes: 03/31/2026 08:58 (54)
Complete: 🔍
Cache ID: 99:E2E:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸