CVE-2026-57348
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Server Side Request Forgery (SSRF) in Paid Member Subscriptions <= 3.0.4 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnauthenticated Server Side Request Forgery (SSRF) vulnerability in the Paid Member Subscriptions WordPress plugin versions 3.0.4 and below allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Paid Member Subscriptions plugin is installedNavigate to WordPress Admin > Plugins and look for 'Paid Member Subscriptions' in the installed plugins list, or inspect the /wp-content/plugins/ directory for the paid-member-subscriptions folderAffected if Plugin is present on the WordPress site
-
Check the installed version numberIn WordPress Admin > Plugins > Installed Plugins, find Paid Member Subscriptions and read the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/paid-member-subscriptions/includes/ or check the readme.txt file for the Version: fieldAffected if Version is 3.0.4 or lower (any version from initial release up to and including 3.0.4)
-
Confirm the plugin is activeIn WordPress Admin > Plugins, verify that Paid Member Subscriptions shows 'Active' status rather than 'Inactive'Affected if Plugin is active and accessible to unauthenticated attackers
-
Inspect network logs for suspicious outbound requestsReview server access logs or web application firewall logs for unusual outbound HTTP requests originating from the web server to internal IP ranges (127.0.0.1, 10.0.0.0/8, 192.168.0.0/16) or unexpected external domains that were not initiated by legitimate admin actionsAffected if Outbound HTTP requests to internal infrastructure or unexpected external hosts are present in logs
A WordPress site with Paid Member Subscriptions plugin installed, active, and running version 3.0.4 or below is affected by this unauthenticated SSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Paid Member Subscriptions to a version newer than 3.0.4. If immediate update is not possible, deploy a WAF rule to block SSRF attack patterns and consider restricting outgoing network requests from the web server.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57348 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data