dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-57407

HIGH · 7.2 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
Server-Side Request Forgery (SSRF) vulnerability in WP Swings PDF Generator for WordPress pdf-generator-for-wp allows Server Side Request Forgery.This issue affects PDF Generator for WordPress: from n/a through <= 1.6.2.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in the PDF Generator for WordPress plugin allows attackers to make the server perform arbitrary requests to internal or external resources. This could enable access to internal services, cloud metadata endpoints, or internal network infrastructure.

MitigationUpdate to the latest version of the plugin if available. If no patch exists, disable the plugin or implement network-level controls to restrict outbound requests from the web server.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate installed plugin version
    In WordPress admin, navigate to Plugins > Installed Plugins and find 'PDF Generator for WordPress'. The version number is displayed under the plugin name. Alternatively, check the main plugin file (e.g., wp-content/plugins/pdf-generator-for-wp/pdf-generator-for-wp.php) and look for the 'Version' header comment.
    Affected if The installed version cannot be confirmed as the latest patched version, or the version is unknown/unreadable.
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that 'PDF Generator for WordPress' shows as 'Active' under the plugin status.
    Affected if The plugin is active and running on the WordPress site.
  3. Identify PDF generation endpoint accessibility
    Check if the plugin exposes any endpoint that accepts URLs for PDF conversion. Common paths include /wp-json/pdf-generator/v1/generate or similar REST API routes. Use a web crawler or check plugin source code for functions handling URL parameters (look for 'url', 'link', or 'source' parameters in AJAX handlers or REST routes).
    Affected if An endpoint accepting user-supplied URLs is publicly accessible without authentication or with low-privilege access.
  4. Review server access logs for suspicious outbound requests
    Examine web server access logs (Apache: access_log, Nginx: access.log) for the WordPress site. Look for repeated POST/GET requests to plugin endpoints that may indicate SSRF probing, or grep for requests from your server to unusual internal IP ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x) or cloud metadata endpoints (169.254.169.254).

Your environment is affected if the PDF Generator for WordPress plugin is active, running an unpatched version, and exposes an endpoint that accepts URLs without proper validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin if available. If no patch exists, disable the plugin or implement network-level controls to restrict outbound requests from the web server.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57407 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57407 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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