dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-1750

HIGH · 8.8 CVSS v3.1 Published 2026-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Ecwid by Lightspeed Ecommerce Shopping Cart plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 7.0.7. This is due to a missing capability check in the 'save_custom_user_profile_fields' function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to supply the 'ec_store_admin_access' parameter during a profile update and gain store manager access to the 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 Ecwid WordPress plugin fails to enforce authorization in the save_custom_user_profile_fields function, allowing authenticated users with minimal subscriber-level permissions to send the ec_store_admin_access parameter during profile updates and escalate their privileges to store manager.

MitigationUpdate the Ecwid by Lightspeed plugin to version 7.0.8 or later which includes proper capability validation for the profile update function.

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
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. Identify Ecwid plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ecwid by Lightspeed' or check the file /wp-content/plugins/ecwid-wordpress-plugin/ for existence. Alternatively, check the plugin header in ecwid-wordpress-plugin.php for Version information.
    Affected if The plugin is installed and the version is below 7.0.8
  2. Confirm plugin version number
    Read the Version field from the plugin header in /wp-content/plugins/ecwid-wordpress-plugin/ecwid-wordpress-plugin.php or view it in the WordPress Plugins admin page. Compare against 7.0.8.
    Affected if Installed version is lower than 7.0.8
  3. Verify subscriber role exists and has access
    Go to Users > Users List in WordPress admin. Check if any users have the 'Subscriber' role. Then test if subscribers can access /wp-admin/profile.php to update their own user profile.
    Affected if Subscriber role exists and can access profile update page
  4. Check for ec_store_admin_access parameter in profile handling
    Inspect the save_custom_user_profile_fields function in the plugin code at /wp-content/plugins/ecwid-wordpress-plugin/. Look for direct acceptance of ec_store_admin_access POST parameter without capability checks.
    Affected if The code accepts ec_store_admin_access parameter from profile updates without verifying administrator capabilities

The environment is affected if the Ecwid by Lightspeed plugin is installed with a version lower than 7.0.8 and the vulnerable save_custom_user_profile_fields function processes the ec_store_admin_access parameter without proper authorization checks.

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 Ecwid by Lightspeed plugin to version 7.0.8 or later which includes proper capability validation for the profile update function.

Recommended fix High confidence

Plugin version 7.0.8 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Ecwid by Lightspeed Ecommerce Shopping Cart' plugin
  4. Check the current version number
  5. Update the plugin to the latest available version (version 7.0.8 or higher)
  6. Verify the update was successful
  7. Test that subscriber-level users can no longer modify the ec_store_admin_access profile field

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