CVE-2019-11565

Print My Blog <= 1.6.6 - Server-Side Request Forgery

2019-04-27 00:00

Strategic Overview

Status: Patched in 1.6.7
Affected Plugin: Print My Blog – Print, PDF, & eBook Converter WordPress Plugin
Affected Version: <= 1.6.6
CVSS: 9.8Critical
Weakness type: CWE-918 · Server-Side Request Forgery (SSRF)
CVE: CVE-2019-11565

View all Print My Blog – Print, PDF, & eBook Converter WordPress Plugin vulnerabilities

At a glance

CVE-2019-11565 is a critical-severity Server-Side Request Forgery (SSRF) vulnerability in the Print My Blog WordPress plugin, affecting versions <= 1.6.6. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.6.7; sites on affected versions should update now. Disclosed April 2019, reported by Magnus K. Stubman.

Vulnerability Overview

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

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Print My Blog <= 1.6.6 takes a caller who can reach the endpoint. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Print My Blog the fix is 1.6.7: builds <= 1.6.6 are affected, anything from 1.6.7 onward is not.

Remediation

Update to version 1.6.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Print My Blog: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Print My Blog 1.6.7 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2019-11565 https://www.wordfence.com/threat-intel/vulnerabilities/id/23fbb011-cf60-4c75-ac68-b5d0dfa3c356 https://nvd.nist.gov/vuln/detail/CVE-2019-11565

Related records

Other vulnerabilities in Print My Blog – Print, PDF, & eBook Converter WordPress Plugin

CVSS Vector

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/