dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-2169

HIGH · 7.3 CVSS v3.1 Published 2025-03-11
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 WPCS – WordPress Currency Switcher Professional plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.2.0.4. 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 WPCS WordPress plugin up to version 1.2.0.4 contains an arbitrary shortcode execution vulnerability. The plugin fails to properly validate user-supplied input before passing it to the do_shortcode() function, allowing unauthenticated attackers to execute any registered WordPress shortcode.

MitigationUpdate the WPCS plugin to version 1.2.0.5 or later which contains proper input validation. If no update is available, disable the plugin until a patch 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
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. Verify WPCS plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WPCS' or 'WooCommerce Product Catalog' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wpcs' or similar.
    Affected if The WPCS plugin is found in the plugins directory
  2. Check installed WPCS version
    In WordPress admin > Plugins, locate WPCS and view the plugin details to see the version number. Alternatively, check the main plugin file (e.g., wpcs.php or index.php) for the 'Version' header in the plugin comment block.
    Affected if The version listed is 1.2.0.4 or earlier
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the WPCS plugin shows as 'Active' under the plugin status.
    Affected if Plugin is active and version is 1.2.0.4 or earlier - the vulnerable code path is reachable
  4. Identify the vulnerable code location (optional)
    If code access is available, search plugin files for 'do_shortcode' calls that process user-supplied input without sanitization, typically in frontend-facing AJAX handlers or shortcode processors.
    Affected if Unsanitized do_shortcode() calls handling request parameters exist in the plugin code

You are affected if the WPCS plugin is installed, active, and the version is 1.2.0.4 or earlier since the vulnerability allows unauthenticated shortcode execution in these versions.

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 WPCS plugin to version 1.2.0.5 or later which contains proper input validation. If no update is available, disable the plugin until a patch is released.

Recommended fix Moderate confidence

Latest version higher than 1.2.0.4 (check WordPress Plugin Repository for current release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'The WPCS – WordPress Currency Switcher Professional' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly on the frontend

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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