dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-9054

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 MultiLoca - WooCommerce Multi Locations Inventory Management plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'wcmlim_settings_ajax_handler' function in all versions up to, and including, 4.2.8. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 MultiLoca plugin's 'wcmlim_settings_ajax_handler' function lacks proper capability checks, allowing unauthenticated attackers to directly modify WordPress options via AJAX. Attackers can enable user registration and set the default role to Administrator, effectively creating admin accounts and gaining full site control.

MitigationUpdate the plugin to version 4.2.9 or later which includes the missing capability check. If no patched version exists, disable the plugin or add a WAF rule to block unauthenticated requests to the vulnerable AJAX endpoint.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify MultiLoca plugin is installed
    Navigate to WordPress admin > Plugins, or inspect the plugin directory (wp-content/plugins/) for a folder named 'multi-loca', 'multiloca', or similar variant containing 'wcmlim' in file names
    Affected if Plugin folder exists in wp-content/plugins/
  2. Determine installed plugin version
    Check the plugin's main PHP file for a version constant or header comment, typically found in the main plugin file (often named plugin-name.php)
    Affected if Version is below 4.2.9 or version cannot be determined (indicating older unmaintained installation)
  3. Confirm AJAX endpoint is accessible
    Test unauthenticated access to the endpoint: make a POST request to /wp-admin/admin-ajax.php with action=wcmlim_settings_ajax_handler (no nonce required for vulnerable versions)
    Affected if Request returns a valid response rather than a 401/403 error or requires authentication
  4. Inspect WordPress user registration settings
    Go to WordPress admin > Settings > General, or query the database: SELECT option_value FROM wp_options WHERE option_name IN ('users_can_register', 'default_role')
    Affected if users_can_register is set to '1' AND default_role is set to 'administrator'
  5. Check for unauthorized admin accounts
    Query the users table: SELECT * FROM wp_users WHERE ID NOT IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%' AND user_id IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'created_by')); Or review user list in admin for unknown admins
    Affected if Unexpected administrator accounts exist that were not created by known administrators

You are affected if the MultiLoca plugin is installed with a version prior to 4.2.9 and the AJAX endpoint is accessible without authentication, or if user registration has been enabled with administrator as the default role.

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 4.2.9 or later which includes the missing capability check. If no patched version exists, disable the plugin or add a WAF rule to block unauthenticated requests to the vulnerable AJAX endpoint.

Recommended fix Moderate confidence

Version higher than 4.2.8 (check WordPress plugin repository or vendor for latest stable release)

  1. 1. Log in to the WordPress admin dashboard with administrative privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the MultiLoca - WooCommerce Multi Locations Inventory Management plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version that contains the security fix
  5. 5. Verify the plugin has been updated to a version higher than 4.2.8
  6. 6. Confirm that the 'wcmlim_settings_ajax_handler' function now includes proper capability checks
  7. 7. Test that the AJAX handler properly validates user permissions before allowing option changes
  8. 8. Review WordPress users to ensure no unauthorized administrator accounts were created

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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