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

CVE-2025-14793

MEDIUM · 5.0 CVSS v3.1 Published 2026-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The DK PDF – WordPress PDF Generator plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.3.0 via the 'addContentToMpdf' function. This makes it possible for authenticated attackers, author level and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 confidence

The DK PDF WordPress plugin versions up to 2.3.0 contain a Server-Side Request Forgery (SSRF) vulnerability in the addContentToMpdf function. Authenticated attackers with author-level permissions or higher can leverage this to make arbitrary HTTP requests from the server, potentially accessing internal services and sensitive information from local networks that should not be publicly exposed.

MitigationUpdate the DK PDF plugin to a version beyond 2.3.0 when available. If no patch exists, remove the plugin and seek an alternative PDF generation solution. Additionally, implement network segmentation and restrict outbound server traffic to prevent internal service exposure.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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. Check DK PDF plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate DK PDF. The version number is displayed below the plugin name. Alternatively, check the main plugin file (dk-pdf.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 2.3.0 or any earlier version (e.g., 2.2.9, 2.2.8, etc.). Versions beyond 2.3.0 are not affected.
  2. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the DK PDF plugin shows as 'Active'.
    Affected if The plugin is active and the version is 2.3.0 or earlier.
  3. Confirm author-level or higher user roles exist
    In WordPress admin, go to Users and review the role assigned to each user. Common author-level roles include Author, Editor, Administrator, and any custom role with publish_posts capability.
    Affected if Any user account with Author, Editor, Administrator, or equivalent permission-level role exists in the WordPress installation.
  4. Review server access logs for suspicious outbound requests
    Examine web server access logs (Apache access.log, Nginx access.log) and/or WordPress debug logs for unusual outgoing HTTP requests originating from the server, particularly to internal IP ranges (e.g., 10.x.x.x, 192.168.x.x, 127.x.x.x) or localhost.
    Affected if Outbound requests to internal/network-local IP addresses are present in logs and originated from plugin functionality.

You are affected if the DK PDF plugin is installed, active, and running version 2.3.0 or earlier, and your site has at least one user with author-level or higher permissions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the DK PDF plugin to a version beyond 2.3.0 when available. If no patch exists, remove the plugin and seek an alternative PDF generation solution. Additionally, implement network segmentation and restrict outbound server traffic to prevent internal service exposure.

Recommended fix Moderate confidence

DK PDF version 2.3.1 or later

  1. Check the current version of the DK PDF plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the plugin is installed, verify if an update is available
  4. Update to the latest version of DK PDF that addresses the SSRF vulnerability (version 2.3.1 or later)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14793 — 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-2025-14793 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