dbcve.org
Welcart E CommerceWordPress extension · Welcart

CVE-2024-42404

HIGH · 8.8 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 2.11.2 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
SQL injection vulnerability in Welcart e-Commerce prior to 2.11.2 allows an attacker who can login to the product to obtain or alter the information stored in the database.

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

SQL injection vulnerability in Welcart e-Commerce prior to version 2.11.2 allows authenticated attackers to inject malicious SQL queries, potentially enabling unauthorized access to, extraction of, or modification of data stored in the database.

MitigationUpgrade Welcart e-Commerce to version 2.11.2 or later to apply the security patch that addresses this SQL injection vulnerability.

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
Welcart E CommerceWordPress extension
Affected:< 2.11.2

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. Check Welcart e-Commerce version
    Navigate to the WordPress admin dashboard, go to Plugins > Installed Plugins, and locate Welcart e-Commerce. The version number is displayed in the plugin description. Alternatively, check the main Welcart plugin file header for the Version field.
    Affected if The installed version is lower than 2.11.2 (for example, 2.11.1, 2.10.x, or earlier)
  2. Confirm user authentication is possible
    Verify that the WordPress site has user registration enabled or has existing user accounts. Check if the wp_users table contains active user records, or confirm that the site allows subscriber-level or higher user registrations.
    Affected if The site has at least one registered user account with appropriate privileges, allowing authenticated access to the vulnerable endpoint
  3. Identify if Welcart core functionality is active
    Check that the Welcart plugin is activated and the usc-e-shop functionality is running. Look for the Welcart menu items in the WordPress admin sidebar, which indicates the plugin core is loaded.
    Affected if The Welcart plugin is active and its core e-commerce modules are loaded and operational

The environment is affected if Welcart e-Commerce version is below 2.11.2 and the plugin is active with authenticated user access possible.

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

Upgrade Welcart e-Commerce to version 2.11.2 or later to apply the security patch that addresses this SQL injection vulnerability.

Recommended fix High confidence

Welcart E Commerce 2.11.2

  1. 1. Create a complete backup of the WordPress site and database before proceeding with any updates.
  2. 2. Navigate to the WordPress admin dashboard and update Welcart E Commerce plugin to version 2.11.2 or later through Plugins > Installed Plugins > Update Now.
  3. 3. Alternatively, manually upload Welcart E Commerce version 2.11.2 or later via Plugins > Add New > Upload Plugin.
  4. 4. After updating, verify the plugin version shows 2.11.2 or newer in the installed plugins list.
  5. 5. Test critical e-commerce functionality (product display, cart, checkout) to ensure the update did not introduce issues.

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

Fix this in Welcart E Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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