dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-3124

HIGH · 7.5 CVSS v3.1 Published 2026-03-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Download Monitor WordPress plugin (versions up to 5.1.7) contains an IDOR vulnerability in the executePayment() function. Due to missing validation on a user-controlled key, unauthenticated attackers can exploit a mismatch between PayPal transaction tokens and local orders to finalize arbitrary high-value orders using payment tokens from low-cost purchases, enabling theft of paid digital goods.

MitigationUpdate the Download Monitor plugin to version 5.1.8 or later. The fix requires implementing proper validation of the PayPal transaction token against the corresponding local order in the executePayment() function to ensure the token matches the intended order.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Download Monitor plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Download Monitor' in the list, or check the /wp-content/plugins/ directory for the download-monitor folder
    Affected if Download Monitor plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find Download Monitor, and note the version number displayed under the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/download-monitor/includes/class-hooks.php or similar main file for the 'Version' comment
    Affected if Version is 5.1.7 or lower
  3. Verify payment processing is enabled
    Check if Download Monitor's e-commerce/payment features are active. Go to Downloads > Settings > E-Commerce (or similar payment configuration page) and see if payment processing is turned on
    Affected if Payment/e-commerce functionality is enabled in Download Monitor settings
  4. Confirm PayPal integration is configured
    Navigate to the payment gateway settings (usually under Downloads > Settings > Payment Gateways or similar) and check if PayPal is listed as an active or configured payment method
    Affected if PayPal payment gateway is configured or enabled as a payment option

The environment is affected if Download Monitor plugin version 5.1.7 or lower is installed with payment processing and PayPal gateway enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Download Monitor plugin to version 5.1.8 or later. The fix requires implementing proper validation of the PayPal transaction token against the corresponding local order in the executePayment() function to ensure the token matches the intended order.

Recommended fix Moderate confidence

Download Monitor version 5.1.8 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Download Monitor' plugin
  4. 4. Check the current installed version under the plugin name
  5. 5. If the installed version is 5.1.7 or earlier, navigate to Plugins > Add New > Upload Plugin (or check for update via WordPress updates)
  6. 6. Update to version 5.1.8 or later
  7. 7. Verify the update completed successfully and the new version is reflected in the plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3124 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data