dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-13320

HIGH · 7.5 CVSS v3.1 Published 2025-03-07
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 CURCY - WooCommerce Multi Currency - Currency Switcher plugin for WordPress is vulnerable to SQL Injection via the 'wc_filter_price_meta[where]' parameter in all versions up to, and including, 2.3.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers 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 CURCY WooCommerce Multi Currency plugin fails to properly escape the 'wc_filter_price_meta[where]' parameter and lacks prepared statements in its SQL queries, allowing unauthenticated attackers to inject arbitrary SQL commands and extract sensitive data from the database.

MitigationUpdate the CURCY plugin to version 2.3.7 or later. If updates are unavailable, disable the plugin until a patched version is released.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify CURCY plugin is installed
    Navigate to WordPress admin > Plugins and locate the CURCY WooCommerce Multi Currency plugin, or inspect the wp-content/plugins directory for a folder containing woo-multi-currency or curcy
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the CURCY plugin details to view the version number, or open the main plugin PHP file in the plugin folder and look for the Version header in the plugin comment block
    Affected if Version is lower than 2.3.7
  3. Inspect HTTP request logs for vulnerable parameter
    Search web server access logs, WordPress debug logs, or WAF/proxy logs for requests containing the parameter wc_filter_price_meta[where], which may appear in POST or GET requests
    Affected if These requests are visible in logs and the plugin version is below 2.3.7
  4. Check plugin files for SQL query handling
    Examine CURCY plugin PHP files, particularly those handling price filtering or meta queries, for direct use of the wc_filter_price_meta[where] variable in SQL queries without prepare() statements or proper escaping
    Affected if The vulnerable code pattern exists and version is below 2.3.7

The environment is affected if the CURCY WooCommerce Multi Currency plugin is installed with a version lower than 2.3.7

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 CURCY plugin to version 2.3.7 or later. If updates are unavailable, disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Version 2.3.7 or later (latest available version from the developer)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the CURCY - WooCommerce Multi Currency - Currency Switcher plugin
  4. Check the current version number (should be 2.3.6 or lower)
  5. Navigate to Plugins > Add New > Upload Plugin (or update via WordPress updates if available)
  6. Upload and install the latest version of the plugin (version higher than 2.3.6)
  7. Verify the update was successful by checking the plugin version
  8. Clear any caching mechanisms if the site uses caching
Caveat Review plugin settings and test currency switching functionality after upgrade to ensure compatibility with your WooCommerce version

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 / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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