dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4094

HIGH · 8.1 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 FOX – Currency Switcher Professional for WooCommerce plugin for WordPress is vulnerable to unauthorized data loss due to a missing capability check on the 'admin_head' function in all versions up to, and including, 1.4.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete the entire multi-currency configuration by visiting any wp-admin page with the `woocs_reset` parameter appended. Additionally, because no nonce is verified, this is also exploitable via Cross-Site Request Forgery against any administrator. The vulnerability may also be exploited by Subscriber-level users if the site is configured to allow Subscriber access to 'wp-admin' pages.

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 FOX Currency Switcher Professional plugin for WooCommerce lacks proper authorization checks on the admin_head function, allowing any authenticated user with Contributor-level access or higher to reset all multi-currency configuration by adding the 'woocs_reset' parameter to any wp-admin URL. Additionally, the absence of nonce verification enables CSRF attacks against administrators, and Subscriber-level users can exploit this if granted wp-admin access.

MitigationUpdate the plugin to version 1.4.6 or later which includes proper capability checks using current_user_can() and nonce verification for the reset functionality. Until then, restrict wp-admin access for Contributor/Subscriber roles.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and locate 'FOX Currency Switcher Professional' or 'Woocs' in the installed plugins list. Note the installed version number displayed.
    Affected if The plugin is installed and the version is below 1.4.6
  2. Check user role permissions for wp-admin
    Review which user roles (Contributor, Subscriber, etc.) have access to wp-admin/dashboard. Go to Users > Users in WordPress admin and check role assignments, or inspect role capabilities via Users > Roles if a role manager plugin is installed.
    Affected if Contributor, Subscriber, or other low-privilege roles have wp-admin access
  3. Test for the woocs_reset vulnerability
    As a user with Contributor-level access, add '?woocs_reset=1' to any wp-admin page URL (e.g., /wp-admin/?woocs_reset=1) and observe if the multi-currency configuration gets reset.
    Affected if The reset executes without prompting for admin credentials or requiring higher privileges
  4. Verify capability check in plugin code
    If you have file access, examine the plugin file (typically in wp-content/plugins/woocommerce-currency-switcher or similar) for the admin_head function and look for current_user_can() capability checks before executing woocs_reset functionality.
    Affected if No current_user_can() check or no nonce verification exists before the reset operation

The environment is affected if the FOX Currency Switcher Professional plugin version is below 1.4.6 AND low-privilege users (Contributor/Subscriber) have wp-admin access, allowing them to reset currency configuration without proper authorization.

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 version 1.4.6 or later which includes proper capability checks using current_user_can() and nonce verification for the reset functionality. Until then, restrict wp-admin access for Contributor/Subscriber roles.

Recommended fix High confidence

1.4.6 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'FOX – Currency Switcher Professional for WooCommerce' plugin
  4. Check the current version number of the plugin
  5. Update the plugin to the latest available version (1.4.6 or later) by clicking 'Update Now' or by downloading from wordpress.org
  6. After updating, verify the multi-currency configuration is intact by visiting the plugin settings page
  7. If the configuration was deleted, reconfigure the currency settings as needed

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-4094 — 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-4094 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