dbcve.org
Welcart E CommerceWordPress extension · Welcart

CVE-2022-41840

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 2.7.8 or later.
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
Unauth. Directory Traversal vulnerability in Welcart eCommerce plugin <= 2.7.7 on WordPress.

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

This is an unauthenticated directory traversal vulnerability in the Welcart eCommerce WordPress plugin affecting versions 2.7.7 and earlier. The flaw allows remote attackers to access files outside the web root directory via specially crafted directory traversal sequences in HTTP requests, potentially exposing sensitive system files.

MitigationUpdate the Welcart eCommerce plugin to the latest version immediately. If immediate updating is not feasible, consider disabling the plugin or deploying a WAF rule to block directory traversal patterns.

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.7.8

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. Verify Welcart eCommerce plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder containing 'welcart' or 'usc-e-shop'
    Affected if The Welcart eCommerce plugin is found in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, click on the Welcart plugin to view its details, or open the main plugin file (usually includes/version.php or readme.txt) and locate the Version field
    Affected if The installed version is 2.7.7 or earlier, or any version below 2.7.8
  3. Identify exposed plugin endpoints
    Review web server access logs for requests to WordPress AJAX handlers or plugin-specific PHP files that may handle file operations. Common paths include /wp-admin/admin-ajax.php or /wp-content/plugins/usc-e-shop/ endpoints
    Affected if HTTP requests to Welcart plugin files are visible in logs or accessible from the web
  4. Check for directory traversal attempts
    Search access logs for patterns containing ../ or ..\ in the query string or URI, particularly targeting Welcart plugin endpoints. Use grep or log analysis tools to find traversal sequences
    Affected if Evidence exists of directory traversal patterns being processed by the plugin (successful 200 responses or file inclusion attempts)
  5. Inspect plugin file handling code
    If codebase access is available, examine the Welcart plugin PHP files for functions that handle file paths (e.g., include, require, file_get_contents, readfile) without proper sanitization of user input
    Affected if File handling functions accept unsanitized user-supplied paths capable of traversing directories

You are affected if the Welcart eCommerce plugin version is 2.7.7 or earlier and the plugin is actively handling HTTP requests without directory traversal protection.

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.7.8 or later
Fixed in 2.7.8
Interim mitigation

Update the Welcart eCommerce plugin to the latest version immediately. If immediate updating is not feasible, consider disabling the plugin or deploying a WAF rule to block directory traversal patterns.

Recommended fix High confidence

Welcart eCommerce 2.7.8

  1. Backup your WordPress site before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate Welcart eCommerce in the plugin list
  5. If an update is available, click 'Update Now' to upgrade to version 2.7.8
  6. Alternatively, download Welcart eCommerce version 2.7.8 from the official WordPress plugin repository and upload it manually
  7. After updating, verify the plugin version shows 2.7.8 or higher in the Plugins list

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

Fix this in Welcart E Commerce 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 the upgrade done

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-2022-41840 — 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-2022-41840 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