dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-13750

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Multilevel Referral Affiliate Plugin for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'orderby' parameter in all versions up to, and including, 2.28 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Multilevel Referral Affiliate Plugin for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the 'orderby' parameter in versions up to 2.28. Authenticated attackers with Subscriber-level access can inject malicious SQL queries due to insufficient escaping and lack of prepared statements in the existing query.

MitigationUpdate the plugin to version 2.29 or later which contains the security fix. If immediate updating is not possible, consider disabling the plugin or deploying a WAF rule to block SQL injection attempts via the orderby parameter.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Locate the plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Find 'Multilevel Referral Affiliate Plugin for WooCommerce' and check the version number displayed below the plugin name. Alternatively, inspect the plugin's main PHP file header or check the version in the plugin's readme.txt file within the plugin directory.
    Affected if The version listed is 2.28 or lower.
  2. Verify the plugin is active
    Confirm that the Multilevel Referral Affiliate Plugin for WooCommerce is currently activated on the WordPress site. This can be done via Plugins > Installed Plugins or by checking wp_options table for the active_plugins option.
    Affected if The plugin is active and the version is 2.28 or lower.
  3. Confirm WooCommerce is installed
    Verify that WooCommerce is installed and active on the same WordPress installation. This plugin is specifically for WooCommerce, and the vulnerable code executes within WooCommerce query contexts.
    Affected if WooCommerce is active and the plugin version is 2.28 or lower.
  4. Check for subscriber-level user accounts
    Review WordPress user roles in Users > All Users to identify any accounts with Subscriber role. The vulnerability is exploitable by users with Subscriber-level access.
    Affected if Subscriber-level users exist and the plugin version is 2.28 or lower.

A user is affected if the Multilevel Referral Affiliate Plugin for WooCommerce is active at version 2.28 or lower and WooCommerce is installed, regardless of whether subscriber accounts actively exploit the SQL injection vulnerability.

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 plugin to version 2.29 or later which contains the security fix. If immediate updating is not possible, consider disabling the plugin or deploying a WAF rule to block SQL injection attempts via the orderby parameter.

Recommended fix High confidence

Version 2.29 or later (the first version after 2.28 that addresses the SQL Injection vulnerability)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Multilevel Referral Affiliate Plugin for WooCommerce'
  4. Check the current version installed
  5. If version is 2.28 or lower, click 'Update Now' to update to the latest version (2.29 or higher)
  6. Alternatively, download the latest version from wordpress.org/plugins/multilevel-referral-affiliate-plugin-for-woocommerce/ and upload manually
  7. After update, verify the plugin is running version 2.29 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13750 — 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-2024-13750 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