dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-13487

HIGH · 7.3 CVSS v3.1 Published 2025-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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 The CURCY – Multi Currency for WooCommerce – The best free currency exchange plugin – Run smoothly on WooCommerce 9.x plugin for WordPress is vulnerable to arbitrary shortcode execution via the get_products_price() function in all versions up to, and including, 2.2.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

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 – Multi Currency for WooCommerce plugin contains a vulnerability in the get_products_price() function that fails to properly validate input before passing it to do_shortcode(). This allows unauthenticated attackers to inject and execute arbitrary WordPress shortcodes, potentially leading to data exposure or further compromise.

MitigationUpdate the plugin to version 2.2.6 or later once available. If no patch exists, consider disabling the plugin temporarily or deploying WAF rules to block requests attempting to exploit the do_shortcode() function.

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
Low
Integrity
Low
Availability
Low

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

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 CURCY plugin is installed
    Navigate to WordPress admin > Plugins and verify the 'CURCY - Multi Currency for WooCommerce' plugin appears in the list of installed plugins
    Affected if plugin is installed and active
  2. Check installed version number
    In the Plugins list, locate CURCY and view the version number displayed under the plugin name. Compare this to version 2.2.6 (the patched version)
    Affected if installed version is lower than 2.2.6 or version cannot be determined
  3. Verify plugin is functional
    Visit the site frontend and confirm the currency converter functionality is working (e.g., currency switcher widget visible, prices converting). This indicates get_products_price() is being executed
    Affected if plugin is active and frontend currency conversion is working, making the vulnerable code path reachable
  4. Inspect get_products_price function for input validation
    Access the plugin source code via file manager or FTP, locate the get_products_price() function in the main plugin file, and examine whether input parameters are sanitized/validated before being passed to do_shortcode()
    Affected if no input validation is found before do_shortcode() call in this function

You are affected if the CURCY plugin is installed with a version below 2.2.6 and the currency conversion feature is active on your site, enabling the unauthenticated shortcode 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.2.6 or later once available. If no patch exists, consider disabling the plugin temporarily or deploying WAF rules to block requests attempting to exploit the do_shortcode() function.

Recommended fix High confidence

Version 2.2.6 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'CURCY – Multi Currency for WooCommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version (2.2.6 or later)
  5. 5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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