Print My Blog – Print, PDF, & eBook Converter <= 3.15.8 - Unprotected AJAX Actions

2022-06-20 00:00
Anonymous

Strategic Overview

Status
Patched in 3.15.9
Affected Plugin
Print My Blog – Print, PDF, & eBook Converter WordPress Plugin
Affected Version
<= 3.15.8
CVSS
6.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Print My Blog – Print, PDF, & eBook Converter WordPress Plugin vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Print My Blog WordPress plugin, affecting versions <= 3.15.8. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.15.9; sites on affected versions should update now. Disclosed June 2022.

Vulnerability Overview

The Print My Blog – Print, PDF, & eBook Converter plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on several functions hooked via AJAX actions in versions up to, and including, 3.15.8. This makes it possible for authenticated attackers with subscriber-level permissions and above to modify the plugin's settings and inject malicious JavaScript. The affected AJAX actions are: wp_ajax_pmb_save_project_main, wp_ajax_pmb_post_search, wp_ajax_pmb_add_print_material, wp_ajax_pmb_reduce_credits, wp_ajax_pmb_report_error, and wp_ajax_pmb_duplicate_print_material. This could also be exploited via Cross-Site Request Forgery.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Print My Blog <= 3.15.8 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Print My Blog the fix is 3.15.9: builds <= 3.15.8 are affected, anything from 3.15.9 onward is not.

Remediation

Update to version 3.15.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Print My Blog 3.15.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/d3004699-3285-426a-8a85-33be6c0c0b6f

Related records

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