Server Side Request Forgery (SSRF) exists in the Print My Blog plugin before 1.6.7 for WordPress via the site parameter.

published 2019-04-27 7y ago modified 2026-06-17 4mo ago also EUVD-2019-3236

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.8%; EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits: 0; none known

Patch / fix

fixed in 1 links 2

print_my_blog_project print_my_blog 1.6.7

Is CVE-2019-11565 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.82% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

dumpco.re http://dumpco.re/bugs/wp-plugin-print-my-blog-ssrf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-918 Server-Side Request Forgery

Technology feeds

WordPress rss critical rss

References

github.com /mnelson4/printmyblog/commit/8584a2839a541eb29fca64252e388c827af3ec21
patch, third-party-advisory
plugins.trac.wordpress.org /changeset?old_path=%2Fprint-my-blog%2Ftrunk&old=2075667&new_path=%2Fprint-my-blog%2Ftrunk&new=2075667
patch, third-party-advisory
dumpco.re /bugs/wp-plugin-print-my-blog-ssrf
exploit, issue-tracking, third-party-advisory
wordpress.org /plugins/print-my-blog/#developers
release-notes, third-party-advisory
wpvulndb.com /vulnerabilities/9263
third-party-advisory

Sources

CVE List CVE-2019-11565
NVD CVE-2019-11565

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.