Safeguard
Vulnerability Analysis•

CVE-2021-24566: High File Inclusion in WooCommerce Currency Switcher

CVE-2021-24566 is a local file inclusion via the woocs shortcode in WooCommerce Currency Switcher before 1.3.7. Update to 1.3.7 and check for new files.

Safeguard Security Team
3 min read

CVE-2021-24566 is a high severity (CVSS 8.8) local file inclusion in the WooCommerce Currency Switcher (WOOCS) plugin, reachable through the woocs shortcode, in versions before 1.3.7. A logged in user may cause files to be included. Update to 1.3.7 or later.

What's affected

  • WOOCS, WooCommerce Currency Switcher by PluginUs.net, versions before 1.3.7, per the NVD record and Jetpack.
  • Fixed in 1.3.7, per Jetpack, who say they reported the problem and the vendor released 1.3.7.
  • Source conflict: NVD scores 8.8 (High) with CWE-22, while the Jetpack write-up lists CVSS 9.9 and CWE-98. Both agree it is an authenticated local file inclusion and that it may allow code execution in some cases.
  • Needs a logged in account with low privileges, such as a customer account on a shop that allows registration.
  • KEV status: false.

How to check if you're exposed

Open the WordPress plugin list, or use WP-CLI.

wp plugin list --fields=name,status,version

Look for woocommerce-currency-switcher below 1.3.7. If your store allows customers to register, then every registered user is a possible source of the request.

What to do now

  1. Update the plugin to 1.3.7 or later.
  2. Review open registration settings. If you do not need customer accounts, disable them.
  3. Check which roles can create posts or content that accepts shortcodes, and tighten them where possible.
  4. Look for unexpected files and modified templates on the server after the period of exposure.
  5. Test currency display and checkout after the update, because stores depend on them.

Why it matters

The record lists CWE-22, path traversal. The Jetpack write-up classes it as improper control of filename for include, CWE-98. In either case a value from the shortcode reaches a file include operation without enough checks. If an attacker can steer which file PHP includes, they can read sensitive files, or run code if they can also place content in a file the server includes.

Shortcodes are easy to overlook, because they look like content and not like input. Any feature that turns user supplied text into server behavior is worth reviewing in your own code and in plugins.

For WordPress sites in general, keep an inventory of installed plugins with their versions, delete the ones you do not use, and apply updates on a schedule. Most plugin flaws are fixed quickly by their authors, and the sites that get hurt are mostly the ones that never applied the fix. A weekly check with WP-CLI takes a few minutes and covers most of the risk.

Quick check

Does an attacker need an account?

Yes. The record says low privileges are needed. On shops that allow customer sign up, getting an account may be easy.

Why do NVD and Jetpack disagree on severity?

NVD says 8.8 and Jetpack says 9.9. Their scoring differs, but both call for updating to 1.3.7.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.