What is the CVSS score of CVE-2026-3881?

CVE-2026-3881 has a CVSS 3.1 base score of 5.8 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-3881?

Yes, a public proof-of-concept exploit is available for CVE-2026-3881. Prioritise patching immediately. EPSS: 0.0%.

Performance Monitor CVE-2026-3881

EUVD-2026-17333 MEDIUM

Server-Side Request Forgery (SSRF) (CWE-918)

2026-03-31 WPScan

GHSA-mxf6-4cfw-jjw8

WordPress SSRF Performance Monitor Unknown

5.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.8 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

PoC Detected

Apr 01, 2026 - 14:24 vuln.today

Public exploit code

EUVD ID Assigned

Mar 31, 2026 - 06:30 euvd

EUVD-2026-17333

Analysis Generated

Mar 31, 2026 - 06:30 vuln.today

CVE Published

Mar 31, 2026 - 06:00 nvd

MEDIUM 5.8

DescriptionCVE.org

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

AnalysisAI

Unauthenticated Server-Side Request Forgery (SSRF) in Performance Monitor WordPress plugin through version 1.0.6 allows remote attackers to perform arbitrary HTTP requests by exploiting insufficient parameter validation. The vulnerability enables attackers without authentication to interact with internal network resources and services accessible from the WordPress server, potentially leading to information disclosure, lateral movement, or interaction with backend systems.

Technical ContextAI

The Performance Monitor WordPress plugin fails to properly validate user-supplied parameters before using them in HTTP requests, creating a classic SSRF vulnerability (CWE class root cause). WordPress plugins operate within the WordPress application context and have broad access to server resources and network connectivity. The vulnerability stems from inadequate input sanitization and validation mechanisms that should restrict request destinations to safe, whitelisted endpoints. Attackers can abuse this to make the vulnerable WordPress server initiate requests to internal IP ranges (127.0.0.1, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), cloud metadata services (AWS/GCP/Azure), or other services the server can reach, bypassing network-level access controls and firewall rules.

RemediationAI

Immediately update the Performance Monitor plugin to a version newer than 1.0.6 if a patched release is available from the WordPress plugin repository. If no patched version is currently available, disable and remove the Performance Monitor plugin until a security update is released by the vendor. Consult the WPScan vulnerability database entry at https://wpscan.com/vulnerability/4b30421e-9848-45ce-87ab-0229d9d7df01/ for updates on patch availability and recommended timeline. As an interim workaround, restrict access to WordPress administrative functions and plugin endpoints using web application firewall rules or IP allowlisting if operationally feasible. Monitor WordPress error logs for suspicious HTTP requests originating from the plugin.