Skip to main content

Paid Member Subscriptions CVE-2026-57348

| EUVDEUVD-2026-41347 HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2026-07-02 Patchstack GHSA-7w66-jfcx-mxqh
7.2
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted request to vulnerable plugin endpoint
  2. Delivery
    Inject attacker-controlled internal URL
  3. Exploit
    Server issues forged outbound request
  4. Execution
    Read response or infer via timing
  5. Impact
    Harvest internal data or cloud metadata

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No authentication or user interaction is required (PR:N/UI:N), and the attack is delivered over the network (AV:N) at low complexity (AC:L) against Paid Member Subscriptions <= 3.0.4, so default installations of the vulnerable plugin are exposed. The practical value of exploitation is limited by the victim's internal environment: the WordPress host must have network reachability to a useful internal target (cloud metadata service, internal API, or intranet host) for the SSRF to yield meaningful data, and egress firewalling or a WAF would blunt it. Because impact is rated C:L/I:L, the flaw supports reconnaissance/limited data disclosure and internal pivoting rather than direct code execution.

Impact

The signals are moderate and internally consistent. CVSS 3.1 is 7.2 (High) with AV:N/AC:L/PR:N/UI:N - network-reachable, low complexity, no privileges or user interaction - which favors easy triggering, but impact is limited to C:L/I:L/A:N (partial confidentiality/integrity, no availability loss), reflecting that SSRF typically yields blind or limited data exposure rather than full compromise. The Scope:Changed elevates the score because the WordPress host can be pivoted against other systems. No EPSS score, no KEV listing, and no POC were provided, so there is no evidence of active or automated exploitation; this reads as a real but not emergency priority. Note a limitation: SSRF real-world severity depends heavily on the victim's internal network (presence of cloud metadata services, unauthenticated internal APIs), which the input data does not describe - impact could be higher or lower than the base score in a given environment.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP request to the vulnerable plugin endpoint with a URL parameter pointing at an internal target, such as http://169.254.169.254/latest/meta-data/ or an internal admin service. The WordPress server dutifully makes the request from its own network position, and the attacker uses the response (or timing/behavioral differences) to enumerate internal hosts or harvest cloud credentials. No public POC was provided, but the low attack complexity (AC:L) and lack of authentication make weaponization straightforward.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 02, 2026

Server-Side Request Forgery in the Paid Member Subscriptions WordPress plugin (versions 3.0.4 and earlier by Cozmoslabs) lets remote unauthenticated attackers coerce the WordPress server into issuing arbitrary outbound HTTP requests. Per the CVSS vector (PR:N, S:C) the flaw is reachable without authentication and crosses a security boundary, enabling attackers to reach internal-only services, cloud metadata endpoints, or other back-end systems the WordPress host can talk to. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; EPSS was not provided.

RemediationAI

Upgrade the Paid Member Subscriptions plugin to a version newer than 3.0.4 as published by Cozmoslabs; the exact fixed version is not confirmed in the provided data, so verify the current patched release via the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/paid-member-subscriptions/vulnerability/wordpress-paid-member-subscriptions-plugin-3-0-4-server-side-request-forgery-ssrf-vulnerability) and the plugin's WordPress.org page before deploying. If immediate patching is not possible, apply compensating controls: place the site behind a WAF with SSRF rules (such as Patchstack's own virtual patching) to filter malicious requests; restrict the WordPress server's outbound egress with a firewall so it can only reach required external endpoints, and explicitly block access to internal ranges (RFC1918) and the cloud metadata IP 169.254.169.254 - the trade-off is that legitimate outbound integrations must be allow-listed or they will break; and enforce IMDSv2 on AWS to blunt metadata theft. As a last resort, deactivate the plugin, accepting loss of membership/paywall functionality.

Affected VersionsENISA

Paid Member Subscriptions n/a ≤3.0.4

Affected Packages

euvd paid_member_subscriptions no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the Paid Member Subscriptions plugin (CPE cpe:2.3:a:cozmoslabs:paid_member_subscriptions), a membership, subscription and paywall solution for WordPress used to gate content and process member sign-ups. The root cause class is CWE-918 (Server-Side Request Forgery): the plugin takes an attacker-influenced value and uses it as the target of a server-initiated network request (e.g., an HTTP fetch via WordPress's HTTP API) without adequately validating or restricting the destination. Because the request originates from the WordPress server, it inherits that server's network position and can address hosts that are not reachable from the public internet, which is why the CVSS scope is marked Changed (S:C).

Know when Paid Member Subscriptions gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 7.2 HIGH

Unauthenticated network SSRF (AV:N/AC:L/PR:N/UI:N) that pivots the server against other systems (S:C) with limited disclosure/manipulation and no availability loss (C:L/I:L/A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

Unauthenticated Server Side Request Forgery (SSRF) in Paid Member Subscriptions <= 3.0.4 versions.

Executive ViewAI

Why It Matters

The Paid Member Subscriptions WordPress plugin (Cozmoslabs) contains a server-side request forgery vulnerability affecting versions 3.0.4 and earlier that allows unauthenticated attackers to access internal systems and backend services protected by your network perimeter. This flaw directly exposes cloud credential endpoints, database servers, and internal APIs to remote compromise without requiring valid user credentials. Any WordPress installation running this plugin represents an immediate data breach and lateral movement risk to backend infrastructure.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Implement egress firewall rules restricting WordPress server outbound connections to approved destinations only; (2) Deploy WAF rules blocking requests to 169.254.169.254 and RFC1918 internal IP ranges from the plugin; (3) Apply network segmentation isolating WordPress servers from backend infrastructure; (4) Enable detailed HTTP request logging from affected servers for SOC monitoring; (5) Disable plugin entirely if business workflow permits until vendor patch released.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Medium
popular WordPress membership plugin, tens of thousands of active installs
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy