dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-11457

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-11
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 EasyCommerce – AI-Powered, Fast & Beautiful WordPress Ecommerce Plugin plugin for WordPress is vulnerable to Privilege Escalation in versions 0.9.0-beta2 to 1.8.2. This is due to the /easycommerce/v1/orders REST API endpoint not properly restricting the ability for users to select roles during registration. This makes it possible for unauthenticated attackers to gain administrator-level 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 EasyCommerce WordPress plugin has a privilege escalation vulnerability in the /easycommerce/v1/orders REST API endpoint. The endpoint fails to properly restrict role selection during user registration, allowing unauthenticated attackers to register with administrator privileges and gain full site access.

MitigationUpdate the EasyCommerce plugin to version 1.8.3 or later. If no patch is available, disable the plugin until a fix is released, or implement custom REST API access controls to restrict role assignment.

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. Confirm EasyCommerce plugin is installed and active
    Go to WordPress admin > Plugins and look for EasyCommerce in the list of active plugins, or use WP-CLI: wp plugin list --status=active --format=csv
    Affected if The plugin appears in the list of active plugins on the site
  2. Identify installed EasyCommerce version
    In WordPress admin > Plugins > EasyCommerce, view the plugin details to see the version number. Alternatively, check the plugin main file header using: grep -i "Version:" /path/to/wp-content/plugins/easycommerce/easycommerce.php
    Affected if The installed version is lower than 1.8.3 (the fixed version)
  3. Verify the vulnerable REST API endpoint is accessible
    Send a GET request to /wp-json/easycommerce/v1/orders or /wp-json/easycommerce/v1/orders endpoint (authenticated if needed by the plugin). Use: curl -s -o /dev/null -w "%{http_code}" https://your-site.com/wp-json/easycommerce/v1/orders
    Affected if The endpoint returns an HTTP 200 response (indicates the plugin REST API is active and potentially reachable)
  4. Confirm user registration is enabled on the site
    In WordPress admin > Settings > General, verify "Anyone can register" is checked and a membership role is selected. Alternatively, check via WP-CLI: wp option get users_can_register
    Affected if The setting "Anyone can register" is enabled on the WordPress site

If EasyCommerce plugin is active, version is below 1.8.3, and user registration is enabled, the site is vulnerable to unauthenticated privilege escalation via the REST API endpoint.

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 EasyCommerce plugin to version 1.8.3 or later. If no patch is available, disable the plugin until a fix is released, or implement custom REST API access controls to restrict role assignment.

Recommended fix Moderate confidence

Version 1.8.3 or later

  1. Check the current version of EasyCommerce plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the EasyCommerce plugin and note the current version number
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. Verify the update was successful and the new version is 1.8.3 or higher
  6. Check the site for any administrator-level users that were created by unauthorized parties and remove them if found
  7. Review user roles and permissions to ensure no unauthorized administrator accounts exist

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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