LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41840: WordPress Welcart eCommerce plugin <= 2.7.7 - Unauth. Directory Traversal vulnerability

Unauth. Directory Traversal vulnerability in Welcart eCommerce plugin <= 2.7.7 on WordPress.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects WordPress sites using Welcart e-Commerce version 2.7.7 or earlier. An unauthenticated internet user may be able to traverse directories and access sensitive files. The main business risk is confidentiality loss, not system takeover based on the provided CVSS data.

Executive priority

Treat as high priority for any public WordPress commerce site. The likely impact is unauthorized access to sensitive files, which can expose credentials, configuration, customer data, or operational secrets depending on server layout.

Technical view

CVE-2022-41840 is a CWE-22 directory traversal issue in Collne Inc. Welcart e-Commerce for WordPress through version 2.7.7. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, high confidentiality impact, and no stated integrity or availability impact.

Likely exposure

Internet-facing WordPress sites running Welcart e-Commerce 2.7.7 or earlier are the relevant exposure. The source bundle does not identify specific vulnerable endpoints, hosting configurations, or compensating controls.

Exploitation context

The vulnerability is unauthenticated and network reachable, which raises urgency. The source bundle says KEV is false and provides no evidence of active exploitation. Patchstack is the cited vulnerability database reference, but no exploit details are provided here.

Researcher notes

Evidence is sparse: the bundle confirms product, version range, CWE, CVSS, and Patchstack reference, but not affected endpoint, proof-of-concept status, exploit activity, or fixed version. Avoid assuming broader WordPress or Welcart versions are affected without vendor confirmation.

Mitigation direction

  • Inventory all WordPress sites for Welcart e-Commerce plugin usage and version.
  • Prioritize sites running version 2.7.7 or earlier.
  • Check vendor or Patchstack guidance for the fixed release before upgrading.
  • Restrict public access where business operations allow until remediation is complete.
  • Review sensitive file exposure risk on affected WordPress hosts.

Validation and detection

  • Confirm the installed Welcart e-Commerce version in WordPress administration or plugin metadata.
  • Verify whether any affected site remains internet accessible.
  • Review web logs for suspicious traversal-like requests targeting WordPress plugin paths.
  • Document remediation status for every affected WordPress instance.
  • Recheck CVE and vendor references for updated remediation details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41840 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-41840Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Collne Inc.Welcart e-Commerce (WordPress plugin)<= 2.7.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.