LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the WordPress Download Monitor plugin can let an unauthenticated attacker mark someone else’s pending paid order as completed. The business risk is theft of paid digital downloads, especially higher-value files, by abusing a payment-token/order mismatch.

Executive priority

High priority for e-commerce WordPress sites selling digital goods. The issue can directly cause revenue loss without requiring attacker login. Non-commerce sites using the plugin have lower practical exposure.

Technical view

CVE-2026-3124 is a CWE-639 insecure direct object reference in Download Monitor through version 5.1.7. The executePayment() function does not sufficiently validate a user-controlled key, allowing a PayPal transaction token to be mismatched with a local order_id and finalize arbitrary pending orders.

Likely exposure

WordPress sites using Download Monitor for paid digital goods, especially with PayPal-backed order completion, are the relevant exposure. The source bundle states versions up to and including 5.1.7 are affected.

Exploitation context

The CVSS vector indicates network exploitation, low complexity, no authentication, and no user interaction. The impact is integrity-focused: unauthorized completion of pending orders. The provided sources do not state active exploitation, and the CVE is not marked KEV.

Researcher notes

The core issue is authorization binding: the payment token and local order identifier are not adequately tied together before order completion. Public sources name the vulnerable function and include a WordPress.org changeset, but the bundle does not name a fixed version.

Mitigation direction

  • Identify all WordPress sites running Download Monitor.
  • Prioritize sites selling paid digital downloads or using PayPal order completion.
  • Check vendor or WordPress plugin guidance for the corrected release.
  • Upgrade beyond affected versions when an official fixed release is available.
  • Temporarily reduce exposure of paid-download workflows if immediate upgrade is unavailable.

Validation and detection

  • Confirm whether Download Monitor is installed and enabled.
  • Record the installed plugin version on each WordPress site.
  • Treat versions up to and including 5.1.7 as affected.
  • Review recent completed orders for payment amount and download-value mismatches.
  • Check order logs for unusual token/order association patterns.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3124 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-3124Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wpchillDownload Monitor0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.