dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-11778

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 – Smoothly on WooCommerce 9.x plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.2.14. 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 for WordPress versions up to 2.2.14 contains an arbitrary shortcode execution vulnerability. The plugin fails to properly validate user input before passing it to the do_shortcode function, allowing unauthenticated attackers to execute arbitrary shortcodes.

MitigationUpdate the plugin to a version beyond 2.2.14 when available, or implement proper input validation/sanitization before any do_shortcode call in the plugin code.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 CURCY plugin directory
    Check your WordPress installation under wp-content/plugins/ for a folder named 'woo-multi-currency', 'multi-currency-for-woocommerce', or similar CURCY-related directory
    Affected if The plugin directory exists in your WordPress plugins folder
  2. Identify the installed version
    Open the main plugin PHP file (usually the first .php file in the plugin folder) and look for the version comment header (e.g., 'Version: x.x.x') or check the plugin header via WordPress admin under Plugins > Installed Plugins
    Affected if The version is 2.2.14 or below, or the version cannot be determined (assume affected)
  3. Confirm the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to see if CURCY - Multi Currency for WooCommerce is activated, or query the wp_options table for the option naming pattern related to this plugin
    Affected if The plugin is active and the version is 2.2.14 or below
  4. Verify unauthenticated access to vulnerable endpoint
    Inspect the plugin code for functions that call do_shortcode with unsanitized user input (look for do_shortcode($_POST, $_GET, or similar direct superglobal usage). Test by sending a request with a harmless shortcode like [wp] to any CURCY-related AJAX or front-end endpoint
    Affected if The plugin processes shortcode calls without validating that the input comes from authorized users or admin pages

Your environment is affected if the CURCY - Multi Currency for WooCommerce plugin is installed, active, and running at version 2.2.14 or lower, as this version allows unauthenticated arbitrary shortcode execution through improper input validation.

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 a version beyond 2.2.14 when available, or implement proper input validation/sanitization before any do_shortcode call in the plugin code.

Recommended fix Moderate confidence

Latest version of CURCY – Multi Currency for WooCommerce plugin beyond 2.2.14

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'The CURCY – Multi Currency for WooCommerce'
  4. Check if an update is available and update to the latest version beyond 2.2.14
  5. Verify the update was applied successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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