dbcve.org
Woocommerce Multilingual \& MulticurrencyWordPress extension · Onthegosystems

CVE-2024-30466

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 5.3.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in OnTheGoSystems WooCommerce Multilingual & Multicurrency.This issue affects WooCommerce Multilingual & Multicurrency: from n/a through 5.3.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

This is a missing authorization vulnerability in the WooCommerce Multilingual & Multicurrency plugin by OnTheGoSystems. The vulnerability allows unauthenticated or unauthorized users to access sensitive functions or data that should require proper capability checks or authentication, likely due to missing capability checks or nonce validations on certain AJAX actions or admin functions.

MitigationUpdate WooCommerce Multilingual & Multicurrency to the latest version (5.3.5 or higher) which should contain the missing authorization checks. If immediate update is not possible, restrict administrative access and review the plugin's AJAX handlers for proper capability checks.

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
Woocommerce Multilingual \& MulticurrencyWordPress extension
Affected:< 5.3.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Locate the WooCommerce Multilingual plugin
    Check your WordPress site's wp-content/plugins directory for a folder named 'woocommerce-multilingual' or 'wpml-woocommerce'. Alternatively, in the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'WooCommerce Multilingual & Multicurrency' by OnTheGoSystems.
    Affected if The plugin is not installed on the WordPress environment.
  2. Identify the installed version
    In the WordPress admin, go to Plugins > Installed Plugins and find the WooCommerce Multilingual entry. The version number is displayed below the plugin name. Alternatively, open the main plugin file (usually wp-content/plugins/woocommerce-multilingual/woocommerce-multilingual.php) and look for the 'Version:' header in the file comments.
    Affected if The plugin version displayed is less than 5.3.5 (for example, 5.3.4, 5.3.3, 5.2.x, etc.).
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that WooCommerce Multilingual & Multicurrency shows as 'Active' (the link reads 'Deactivate' rather than 'Activate').
    Affected if The plugin is active and the version is below 5.3.5.
  4. Check for exposed AJAX endpoints (optional)
    Inspect your site's publicly accessible AJAX endpoints by visiting your site's URL with /wp-admin/admin-ajax.php?action= to see if any WPML-related actions respond without authentication. Note: This requires manual testing and knowledge of the specific AJAX actions exposed by the plugin.
    Affected if The plugin is active, version is below 5.3.5, and AJAX actions related to the plugin can be accessed without proper capability verification.

The environment is affected if WooCommerce Multilingual & Multicurrency by OnTheGoSystems is installed, active, and running a version lower than 5.3.5.

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

Update WooCommerce Multilingual & Multicurrency to the latest version (5.3.5 or higher) which should contain the missing authorization checks. If immediate update is not possible, restrict administrative access and review the plugin's AJAX handlers for proper capability checks.

Recommended fix High confidence

5.3.5

  1. Backup your WordPress site database and files before updating
  2. Navigate to Dashboard > Updates in WordPress admin, or go to Plugins > Installed Plugins
  3. Update WooCommerce Multilingual & Multicurrency to version 5.3.5
  4. Verify the plugin version shows 5.3.5 after update
  5. Test critical multilingual and multicurrency functionality to confirm the fix works

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

Fix this in Woocommerce Multilingual \& Multicurrency Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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