dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-57765

HIGH · 8.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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
Contributor SQL Injection in WP EasyCart <= 5.9.0 versions.

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

Authenticated SQL injection vulnerability in WP EasyCart plugin versions 5.9.0 and below allows users with Contributor-level permissions to execute arbitrary SQL commands via unsanitized input in database queries.

MitigationUpdate WP EasyCart to the latest version or implement proper parameterized queries and input validation on all user-supplied parameters in the plugin's database operations.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L

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. Check WP EasyCart plugin version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, find WP EasyCart and note the version number. Alternatively, open wp-content/plugins/wp-easycart/includes/ec_version.php or check the plugin header in its main PHP file.
    Affected if The installed version is 5.9.0 or below.
  2. Verify Contributor role access exists
    In WordPress admin, go to Users > All Users and check if any users have the Contributor role assigned. Alternatively, query the wp_usermeta table for capability entries containing 'contributor'.
    Affected if At least one user with Contributor-level permissions exists in the WordPress installation.
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that WP EasyCart shows as 'Active'. Alternatively, check the wp_options table for an option_name of 'wp_easycart_version' with an active status.
    Affected if The WP EasyCart plugin is currently activated on the site.
  4. Inspect request handling for the vulnerable endpoint
    If you have file system access, examine the WP EasyCart plugin files for HTTP request handling (typically in admin or ajax handlers) and look for direct use of $_GET, $_POST, or $_REQUEST variables in SQL queries without prepare() or esc_sql() sanitization. Common paths include wp-content/plugins/wp-easycart/ and subdirectories for admin/ajax handlers.
    Affected if Plugin files contain unsanitized SQL queries using request parameters.

A user is affected if WP EasyCart version 5.9.0 or below is installed and active, and any Contributor-level user account exists on the site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP EasyCart to the latest version or implement proper parameterized queries and input validation on all user-supplied parameters in the plugin's database operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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