dbcve.org
Wordpress Currency SwitcherWordPress extension · Pluginus

CVE-2023-51506

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to after 1.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in realmag777 WPCS – WordPress Currency Switcher Professional allows Stored XSS.This issue affects WPCS – WordPress Currency Switcher Professional: from n/a through 1.2.0.

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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability in the WPCS – WordPress Currency Switcher Professional plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized input fields in the currency switcher settings. The injected payloads are stored in the database and execute when administrators or users view affected pages in the WordPress admin dashboard or frontend.

MitigationUpdate to a patched version of the plugin if available. If no update exists, implement output encoding for all currency-related data displayed in pages and apply proper input sanitization (sanitize_text_field, esc_attr, esc_html) to all user-supplied values before storage and before output.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wordpress Currency SwitcherWordPress extension
Affected:<= 1.2.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Verify WordPress Currency Switcher plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WPCS - WordPress Currency Switcher Professional' or similar currency switcher plugin from Pluginus.
    Affected if The plugin is not installed or not present in the plugins list
  2. Check the installed plugin version
    In the plugins list, locate the currency switcher plugin and note the version number displayed below the plugin name.
    Affected if Version is 1.2.0 or lower (any version <= 1.2.0)
  3. Inspect currency settings for unsanitized input
    Go to the plugin settings page (usually under WooCommerce > Currency Switcher or a dedicated WPCS menu). Examine fields where currency names, symbols, or exchange rates can be entered. Look for any HTML, script tags, or javascript: attributes in the stored values.
    Affected if Any currency-related fields contain raw HTML or script tags without proper encoding
  4. Review database for suspicious stored values
    Access the WordPress database (via phpMyAdmin or wp-cli). Query the wp_options table or any wpcs-related tables for option names containing 'currency', 'switcher', or 'wpcs'. Examine the stored values for unescaped characters like <, >, script, or event handlers (onclick, onerror, etc.).
    Affected if Stored option values contain unescaped HTML or JavaScript code
  5. Check frontend and admin pages for XSS execution
    Visit pages where the currency switcher is displayed. View the page source or inspect elements to see if currency data is rendered with proper escaping. Also check the admin dashboard pages where currency settings are displayed.
    Affected if Currency values render as raw HTML or trigger JavaScript when viewed

If the WPCS - WordPress Currency Switcher Professional plugin is installed at version 1.2.0 or lower, the environment is affected by this stored XSS 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
Upgrade available Upgrade to a release after 1.2.0
Interim mitigation

Update to a patched version of the plugin if available. If no update exists, implement output encoding for all currency-related data displayed in pages and apply proper input sanitization (sanitize_text_field, esc_attr, esc_html) to all user-supplied values before storage and before output.

Recommended fix Low confidence

Latest available version of WPCS – WordPress Currency Switcher Professional (version higher than 1.2.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WPCS – WordPress Currency Switcher Professional' in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is functioning correctly and test the currency switching functionality
  7. 7. Clear any caching plugins or server-side caches if applicable

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

Fix this in Wordpress Currency Switcher 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 the upgrade done

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-2023-51506 — 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-2023-51506 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