Fox Currency Switcher Professional For WoocommerceWordPress extension · Pluginus
CVE-2024-30458
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in realmag777 WOOCS – WooCommerce Currency Switcher.This issue affects WOOCS – WooCommerce Currency Switcher: from n/a through 1.4.1.7.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WOOCS – WooCommerce Currency Switcher plugin allows remote attackers to induce authenticated users to execute unwanted actions (such as modifying currency settings) by tricking them into submitting crafted requests.
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
< 1.4.1.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WOOCS plugin is installedCheck WordPress plugins directory for 'woocs' folder, or run: wp plugin list --slug=woocs --status=active --format=jsonAffected if Plugin folder 'woocs' exists in /wp-content/plugins/ and shows as active
-
Check installed plugin versionRead version from plugin header in /wp-content/plugins/woocs/woocs.php or run: wp plugin get woocs --field=versionAffected if Version number is lower than 1.4.1.8
-
Confirm plugin handles currency settingsCheck that currency configuration is accessible at /wp-admin/admin.php?page=wc-settings&tab=woocs, or that WOOCS menu appears in WordPress admin dashboardAffected if Admin can access currency switcher settings without additional protection checks
-
Identify if nonces validate form submissionsInspect PHP files in /wp-content/plugins/woocs/ for wp_verify_nonce or check_admin_referer calls on AJAX and form handlers related to currency settingsAffected if No nonce validation found in currency settings update handlers (files like class-woocs.php, ajax/woocs-ajax.php, or similar)
-
Check referrer validation on admin actionsSearch plugin code for check_ajax_referer or referrer header validation in files handling settings changesAffected if No referrer or origin validation present on POST requests to currency settings endpoints
User is affected if WOOCS plugin is active with version below 1.4.1.8 and lacks proper nonce/referrer validation on its currency settings forms.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.1.8
Implement WordPress nonces on all form submissions and AJAX requests, and add referrer header validation to verify request origin.
WOOCS – WooCommerce Currency Switcher version 1.4.1.8
- Backup your WordPress site and database before proceeding with any updates.
- Navigate to your WordPress admin dashboard > Plugins > Installed Plugins
- Find 'WOOCS – WooCommerce Currency Switcher' (also known as 'Fox Currency Switcher Professional For WooCommerce')
- Click 'Update now' when an update to version 1.4.1.8 is available, or manually upload version 1.4.1.8 of the plugin
- After updating, verify the plugin version shows 1.4.1.8 in the plugins list
- Test that the currency switching functionality works correctly on your WooCommerce store
- 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 Fox Currency Switcher Professional For Woocommerce
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-30458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30458 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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