Skip to content
Fencer Intel
high 8.1

CVE-2021-24636 json

Print My Blog < 3.4.2 - Plugin Deactivation via CSRF

published 5y ago modified 4mo ago also EUVD-2021-11548

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits
0
none known

Summary

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

Patch / fix

  • print_my_blog_project print_my_blog 3.4.2

Is CVE-2021-24636 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

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

Exploits and checks

  • wpscan.com https://wpscan.com/vulnerability/db8ace7b-7a44-4620-9fe8-ddf0ad520f5e referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P

Affected products

  • Unknown Print My Blog – Print, PDF, & eBook Converter WordPress Plugin

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery
Technology feeds

References

Sources

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.