dbcve.org
Welcart E CommerceWordPress extension · Welcart

CVE-2025-47511

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-09
Fix available
A fix is available. Upgrade to 2.11.14 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in info@welcart Welcart e-Commerce usc-e-shop allows Path Traversal.This issue affects Welcart e-Commerce: from n/a through <= 2.11.13.

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

A path traversal vulnerability in Welcart e-Commerce plugin (usc-e-shop) allows attackers to access files outside the restricted directory by manipulating file paths in user-supplied input. The vulnerability exists in versions up to and including 2.11.13.

MitigationApply the latest security patch from Welcart that adds proper input validation and sanitization on file path parameters to prevent directory traversal sequences (e.g., ../). If no patch is available, implement strict validation that only allows whitelisted safe characters and rejects any path containing traversal sequences.

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

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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. Locate Welcart e-Commerce plugin installation
    Check for the plugin directory at wp-content/plugins/usc-e-shop/ or search for 'Welcart' in WordPress plugin list via wp-admin/plugins.php
    Affected if Plugin directory exists in the WordPress installation
  2. Identify installed plugin version
    Open the main plugin file (usc-e-shop/usc-e-shop.php) or readme.txt and locate the Version header comment. Alternatively, check in WordPress admin under Plugins > Welcart e-Commerce
    Affected if Version is 2.11.13 or lower (anything below 2.11.14)
  3. Identify file path handling functionality
    Search the plugin directory for file-related functions handling user input: look for $_GET, $_POST, or $_REQUEST parameters used in file operations like fopen, file_get_contents, include, or similar file functions
    Affected if Plugin code contains file operations accepting user-supplied path parameters without validation
  4. Check for direct exposure of file handling endpoints
    Examine the plugin for PHP files that process file path parameters (search for 'path', 'file', 'download' in parameter names). Check if these endpoints are accessible without authentication or via front-end forms
    Affected if File path parameters in plugin are accessible to unauthenticated or low-privileged users

A user is affected if Welcart e-Commerce plugin version is 2.11.13 or lower AND the plugin's file handling functionality with user-supplied path input is active or exposed.

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.14 or later
Fixed in 2.11.14
Interim mitigation

Apply the latest security patch from Welcart that adds proper input validation and sanitization on file path parameters to prevent directory traversal sequences (e.g., ../). If no patch is available, implement strict validation that only allows whitelisted safe characters and rejects any path containing traversal sequences.

Recommended fix High confidence

Welcart e-Commerce version 2.11.14

  1. 1. Create a full backup of your WordPress site (database and files) before proceeding
  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 upgrade to version 2.11.14 or later
  6. 6. Alternatively, download Welcart e-Commerce version 2.11.14 from the official WordPress plugin repository or Welcart website
  7. 7. If using manual upload, deactivate the current plugin, delete it (data should be preserved if configured correctly), then upload and install the new version
  8. 8. After upgrade, clear any caching systems and test core e-commerce functionality (product pages, cart, checkout, order processing)
Caveat Review Welcart's release notes for 2.11.14 for any compatibility notices with WordPress versions or dependent plugins

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 / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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