dbcve.org
Fox Currency Switcher Professional For WoocommerceWordPress extension · Pluginus

CVE-2023-49834

HIGH · 8.8 CVSS v3.1 Published 2023-12-17
Fix available
A fix is available. Upgrade to 1.4.1.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in realmag777 FOX – Currency Switcher Professional for WooCommerce.This issue affects FOX – Currency Switcher Professional for WooCommerce: from n/a through 1.4.1.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the FOX Currency Switcher Professional plugin for WooCommerce. The vulnerability allows attackers to trick authenticated administrators into performing unintended actions (such as changing currency settings, rates, or plugin configurations) via maliciously crafted requests.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify nonce validation on every state-changing operation.

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
Fox Currency Switcher Professional For WoocommerceWordPress extension
Affected:< 1.4.1.5

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check installed plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins, locate 'Fox Currency Switcher Professional For Woocommerce' by Pluginus Fox, and read the version number displayed under the plugin name. Alternatively, check the main plugin file (usually fox-currency-switcher-professional-for-woocommerce.php) for the 'Version' header in the plugin comment block.
    Affected if The version listed is less than 1.4.1.5 (for example, 1.4.1.4, 1.4.0, etc.)
  2. Verify plugin is active
    In WordPress Admin > Plugins, confirm the Fox Currency Switcher Professional plugin shows as 'Active' (not just installed).
    Affected if The plugin is active and the version is below 1.4.1.5
  3. Inspect for nonce implementation in admin forms
    Access the plugin directory via file manager or FTP (wp-content/plugins/fox-currency-switcher-professional-for-woocommerce), then search plugin PHP files for 'wp_nonce_field' or 'wp_nonce' function calls within admin-facing forms. Use grep or a text editor to search the codebase.
    Affected if No nonce fields are found in admin forms (such as currency settings, rate configuration, or plugin options forms) and the version is below 1.4.1.5
  4. Inspect AJAX endpoints for nonce verification
    Search plugin PHP files for 'admin-ajax.php' or custom AJAX handlers, then verify if these handlers include nonce verification checks using 'check_admin_referer' or 'wp_verify_nonce'. Check files in the includes/ or classes/ directories.
    Affected if AJAX endpoints lack nonce verification logic and the version is below 1.4.1.5

A user is affected if the Fox Currency Switcher Professional for WooCommerce plugin is active at a version lower than 1.4.1.5 and lacks proper nonce validation on admin forms or AJAX endpoints.

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 1.4.1.5 or later
Fixed in 1.4.1.5
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify nonce validation on every state-changing operation.

Recommended fix High confidence

1.4.1.5

  1. Upgrade the FOX – Currency Switcher Professional for WooCommerce plugin to version 1.4.1.5 or later

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

Fix this in Fox Currency Switcher Professional For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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