LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40199: Directory traversal vulnerability in EC-CUBE 3 series (EC-CUBE 3.0.0 to 3.0.18-p4 ) and EC-CUBE 4 series (E...

Directory traversal vulnerability in EC-CUBE 3 series (EC-CUBE 3.0.0 to 3.0.18-p4 ) and EC-CUBE 4 series (EC-CUBE 4.0.0 to 4.1.2) allows a remote authenticated attacker with an administrative privilege to obtain the product's directory structure information.

LowCVSS 2.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2022-40199 is a low-severity directory traversal issue in EC-CUBE ecommerce platforms. An attacker must already have administrative privileges, and the disclosed impact is learning directory structure information. The main business concern is added reconnaissance value if an admin account is compromised.

Executive priority

Treat as routine but real maintenance. Prioritize remediation for internet-facing ecommerce administration portals or environments with weak admin account controls.

Technical view

The vulnerability is CWE-22 in EC-CUBE 3.0.0 through 3.0.18-p4 and EC-CUBE 4.0.0 through 4.1.2. CVSS 3.1 is 2.7, with network access, low attack complexity, high privileges required, no user interaction, and low confidentiality impact only.

Likely exposure

Exposure is limited to organizations running affected EC-CUBE 3 or 4 versions, especially where the administrative interface is reachable and admin accounts are not tightly controlled.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Abuse requires a remote authenticated attacker with administrative privilege, so this is most relevant after credential compromise or malicious insider access.

Researcher notes

Evidence supports authenticated administrative information disclosure only. No exploit details, active exploitation, or exact patch version is provided in the prompt bundle, so remediation should be tied to vendor guidance.

Mitigation direction

  • Check EC-CUBE and JVN guidance for the supported fixed release path.
  • Upgrade affected EC-CUBE installations according to vendor instructions.
  • Restrict administrative access to trusted networks or VPN where feasible.
  • Review administrative users and remove unnecessary privileged accounts.
  • Monitor administrative activity for unusual file or path discovery behavior.

Validation and detection

  • Inventory EC-CUBE deployments and record exact installed versions.
  • Flag EC-CUBE 3.0.0-3.0.18-p4 and 4.0.0-4.1.2 as affected.
  • Confirm whether admin interfaces are internet-accessible.
  • Review admin account MFA, ownership, and recent login history.
  • Check vendor and JVN advisories before closing remediation.
Prepared
Confidence
high
Sources
4

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-40199 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
Low
CVSS
2.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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
3Source 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
2.7CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N1.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.7Low
CVSS 3.1 vector shape for CVE-2022-40199Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EC-CUBE CO.,LTD.EC-CUBE 3 series and EC-CUBE 4 seriesEC-CUBE 3.0.0 to 3.0.18-p4 and EC-CUBE 4.0.0 to 4.1.2Listed
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.