CVE-2024-33594

Leaky Paywall <= 4.20.8 - Missing Authorization to Price Manipulation

2024-04-25 00:00
Joshua Chan

Strategic Overview

Status
Patched in 4.20.9
Affected Plugin
Leaky Paywall
Affected Version
<= 4.20.8
CVSS
5.3Medium
Weakness type
CWE-472 · External Control of Assumed-Immutable Web Parameter
CVE
CVE-2024-33594
View all Leaky Paywall vulnerabilities

At a glance

CVE-2024-33594 is a medium-severity External Control of Assumed-Immutable Web Parameter vulnerability in the Leaky Paywall WordPress plugin, affecting versions <= 4.20.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.20.9; sites on affected versions should update now. Disclosed April 2024, reported by Joshua Chan.

Vulnerability Overview

The Leaky Paywall plugin for WordPress is vulnerable to price manipulation in all versions up to, and including, 4.20.8. This is due to the plugin allowing the price field to be user supplied. This makes it possible for unauthenticated attackers to alter the price of memberships.

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.

CWE-472: External Control of Assumed-Immutable Web Parameter

Reaching this weakness in Leaky Paywall <= 4.20.8 takes a caller who can reach the endpoint. External control of an assumed-immutable parameter means the code trusts a value it believes cannot be changed by the caller, when in fact the request carries it.

Editing that field changes the outcome of the operation, which on commerce plugins means altered prices or totals and on account flows means acting as another user. For Leaky Paywall the fix is 4.20.9: builds <= 4.20.8 are affected, anything from 4.20.9 onward is not.

Remediation

Update to version 4.20.9, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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