CVE-2021-24636

Print My Blog – Print, PDF, & eBook Converter WordPress Plugin <= 3.4.1 - Cross-Site Request Forgery

2021-08-18 00:00
apple502j

Strategic Overview

Status
Patched in 3.4.2
Affected Plugin
Print My Blog – Print, PDF, & eBook Converter WordPress Plugin
Affected Version
<= 3.4.1
CVSS
8.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-24636
View all Print My Blog – Print, PDF, & eBook Converter WordPress Plugin vulnerabilities

At a glance

CVE-2021-24636 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Print My Blog WordPress plugin, affecting versions <= 3.4.1. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.4.2; sites on affected versions should update now. Disclosed August 2021, reported by apple502j.

Vulnerability Overview

The Print My Blog WordPress Plugin before 3.4.2 does not enforce nonce (CSRF) checks, which allows attackers to make logged in administrators deactivate the Print My Blog plugin and delete all saved data for that plugin by tricking them to open a malicious link.

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. A successful exploit has high impact on integrity, availability.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Print My Blog <= 3.4.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Print My Blog the fix is 3.4.2: builds <= 3.4.1 are affected, anything from 3.4.2 onward is not.

Remediation

Update to version 3.4.2, 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 3.4.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24636https://www.wordfence.com/threat-intel/vulnerabilities/id/f44d7a90-330f-42fb-a4f3-427e60ed7af8https://nvd.nist.gov/vuln/detail/CVE-2021-24636

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C