CVE-2026-57348: Unauthenticated SSRF in Paid Member Subscriptions <= 3.0.4
Unauthenticated Server Side Request Forgery (SSRF) vulnerability exists in Paid Member Subscriptions plugin versions up to and including 3.0.4. An attacker can exploit this flaw without needing valid credentials to make the vulnerable server send requests to internal or external systems on their behalf. This could allow unauthorized access to internal services, data exfiltration, or attacks against systems the plugin server can reach.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.2 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-918
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-02 / 2026-07-02
NVD description (verbatim)
Unauthenticated Server Side Request Forgery (SSRF) in Paid Member Subscriptions <= 3.0.4 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-57348 is an SSRF vulnerability (CWE-918) affecting Paid Member Subscriptions <= 3.0.4. The vulnerability permits unauthenticated attackers to craft malicious requests that cause the server to fetch URLs or interact with internal resources. The attack vector is network-based with low complexity, requires no privileges or user interaction, and has a scope change impact. While confidentiality and integrity are partially compromised, availability is not affected per the CVSS 3.1 vector (7.2/HIGH).
Business impact
Organizations relying on the Paid Member Subscriptions plugin face exposure of internal systems and data. An attacker could pivot from the vulnerable plugin to access internal databases, APIs, or microservices not directly exposed to the internet. In subscription-based business models, this could lead to unauthorized access to member data, billing information, or service disruption. The lack of authentication requirement significantly lowers the barrier to exploitation.
Affected systems
Paid Member Subscriptions plugin versions 3.0.4 and earlier are affected. Organizations should verify whether this plugin is active in their environment and confirm their current installed version. If the plugin is disabled or not deployed, risk is mitigated.
Exploitability
This vulnerability is highly exploitable due to the lack of authentication requirements, low attack complexity, and network accessibility. An attacker only needs to craft a malicious request to trigger the SSRF condition; no user interaction is required. The scope change indicates the impact extends beyond the vulnerable component itself, making it a network-reachable attack surface for external threat actors.
Remediation
Update Paid Member Subscriptions to a version newer than 3.0.4. Verify the specific patched version by consulting the vendor's security advisory or plugin repository. Until patching is possible, consider disabling the plugin if not critical to operations, or restrict network access from the plugin server to sensitive internal systems using firewall rules or network segmentation.
Patch guidance
Upgrade Paid Member Subscriptions to a version released after 3.0.4. Confirm patch availability through the plugin's official repository or vendor security advisory before deploying to production. Test the patched version in a staging environment to validate compatibility with your WordPress installation and any dependent functionality.
Detection guidance
Monitor for unusual outbound requests originating from the web server hosting Paid Member Subscriptions, particularly to internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or localhost services. Review access logs for requests containing suspicious URL parameters that reference internal hostnames or IP addresses. Implement Web Application Firewall (WAF) rules to block requests containing common SSRF payloads targeting metadata services or internal endpoints.
Why prioritize this
HIGH CVSS score (7.2) combined with unauthenticated exploitability makes this a priority remediation target. The scope change means exploitation can impact systems beyond the plugin itself. Organizations should prioritize patching before threat actors discover and weaponize this flaw at scale.
Risk score, explained
The CVSS 3.1 score of 7.2 (HIGH) reflects the network attack vector, low complexity, lack of authentication, and scope change. While the impact to confidentiality and integrity is partial (L), the absence of authentication and the cross-boundary impact elevate overall risk. This is not yet a CVSS 9+ critical vulnerability, but it remains significantly above the 'medium' threshold and warrants urgent attention.
Frequently asked questions
Does this vulnerability affect all WordPress sites?
No. Only sites running the Paid Member Subscriptions plugin at version 3.0.4 or earlier are affected. If you do not use this plugin, you are not vulnerable to CVE-2026-57348.
Can this vulnerability be exploited by an authenticated user only?
No. The vulnerability is explicitly unauthenticated, meaning an attacker does not need valid login credentials to trigger it. This significantly increases the risk surface.
What internal systems could an attacker target via SSRF?
An attacker could potentially reach internal databases, microservices, metadata endpoints, admin interfaces, or other services accessible from the web server's network segment but not exposed directly to the internet. The specific risk depends on your network architecture and what services are reachable from the plugin server.
What should I do if I cannot update immediately?
Consider temporarily disabling the Paid Member Subscriptions plugin if it is not critical. Alternatively, implement network segmentation to restrict outbound connections from the plugin server, or use a WAF to block suspicious requests. Monitor logs closely for exploitation attempts while you plan a patching window.
This analysis is based on publicly disclosed vulnerability data as of the publication date. Actual impact and exploitability may vary depending on network architecture, plugin configuration, and deployed mitigations. Verify patch availability and compatibility with your specific WordPress environment before deployment. SEC.co does not provide legal, compliance, or operational advice; consult your security team and vendor advisories for decision-making. Threat intelligence is provided as-is without warranty of timeliness or completeness. Source: NVD (public-domain), retrieved 2026-08-11. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2025-53828HIGHServer-Side Request Forgery in SharePoint for ownCloud Enables Admin Code Execution
- CVE-2026-10055HIGHEclipse Theia SSRF Vulnerability in /services/request-service
- CVE-2026-10068HIGHSSRF in Shibby Tomato 1.28 miniupnpd (Unmaintained)
- CVE-2026-10107HIGHMoviePilot v2 SSRF in Image Proxy Allows Internal Network Access
- CVE-2026-10129HIGHIBM Langflow OSS SSRF Bypass via Redirect Following – HIGH Risk
- CVE-2026-10280HIGHServer-Side Request Forgery in Horizon921 mcpilot 0.1.0
- CVE-2026-10287HIGHSSRF in SourceCodester SEO Meta Tag Extractor 1.0
- CVE-2026-10546HIGHIBM Langflow OSS SSRF via TOCTOU Race Condition