CVE-2026-3124

Download Monitor <= 5.1.7 - Insecure Direct Object Reference to Unauthenticated Arbitrary Order Completion via 'token' and 'order_id'

2026-03-29 12:42
bashu

Strategic Overview

Status
Patched in 5.1.8
Affected Plugin
Download Monitor
Affected Version
<= 5.1.7
CVSS
7.5High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-3124
View all Download Monitor vulnerabilities

At a glance

CVE-2026-3124 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the Download Monitor WordPress plugin, affecting versions <= 5.1.7. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 5.1.8; sites on affected versions should update now. Disclosed March 2026, reported by bashu.

Vulnerability Overview

The Download Monitor plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.7 via the executePayment() function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to complete arbitrary pending orders by exploiting a mismatch between the PayPal transaction token and the local order, allowing theft of paid digital goods by paying a minimal amount for a low-cost item and using that payment token to finalize a high-value order.

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 integrity.

CWE-639: Authorization Bypass Through User-Controlled Key

Download Monitor <= 5.1.7 carries this weakness at executePayment(), and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Download Monitor the fix is 5.1.8: builds <= 5.1.7 are affected, anything from 5.1.8 onward is not.

Remediation

Update to version 5.1.8, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Download Monitor 5.1.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-3124https://www.wordfence.com/threat-intel/vulnerabilities/id/45527d6c-6866-44e6-85c2-5be984afbbc9https://nvd.nist.gov/vuln/detail/CVE-2026-3124

Related records

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