dbcve.org
Welcart E CommerceWordPress extension · Welcart

CVE-2024-45366

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 2.11.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Welcart e-Commerce prior to 2.11.2 contains a cross-site scripting vulnerability. If this vulnerability is exploited, an arbitrary script may be executed on the user's web browser.

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

Welcart e-Commerce plugin before version 2.11.2 contains a cross-site scripting (XSS) vulnerability that allows execution of arbitrary JavaScript in a victim's browser, likely through unsanitized user input being reflected in web pages.

MitigationUpdate Welcart e-Commerce to version 2.11.2 or later to receive the security patch that addresses the XSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Welcart e-Commerce plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Welcart e-Commerce' in the list
    Affected if Plugin is present in the WordPress installation
  2. Determine installed plugin version
    In the Plugins list, click on 'Welcart e-Commerce' details or hover over it to view the version number displayed
    Affected if Version shown is less than 2.11.2 (for example, 2.11.1, 2.10.x, etc.)
  3. Confirm plugin is active
    Check the status indicator next to Welcart e-Commerce in the Plugins list - it must be showing as 'Active' for the XSS to be exploitable
    Affected if Plugin is both installed and active with version below 2.11.2
  4. Identify XSS attack surface
    Review Welcart pages where user input is reflected (such as search fields, product filters, or form submissions) - the vulnerability allows unsanitized input to be rendered in the browser
    Affected if User-controllable input is reflected in Welcart-generated pages without sanitization

The environment is affected if Welcart e-Commerce plugin version is below 2.11.2 and the plugin is active, allowing unsanitized user input to be reflected in web pages.

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

Update Welcart e-Commerce to version 2.11.2 or later to receive the security patch that addresses the XSS vulnerability.

Recommended fix Moderate confidence

2.11.2

  1. 1. Back up your WordPress database and files before performing any upgrade
  2. 2. Log in to your WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Find Welcart E Commerce in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 2.11.2
  6. 6. Alternatively, download Welcart E Commerce version 2.11.2 from the official Welcart website and upload it via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the new version is installed by checking the plugin details
  8. 8. Test critical e-commerce functions (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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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