Skip to content

← Actionable
Low, CVSS 2.7

EC-CUBE Directory traversal vulnerability

CVE-2022-40199GHSA-wjpv-frf2-3r58

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Packagist ec-cube/ec-cube

    Affected
    >= 3.0.0, <= 3.0.18-p4>= 4.0.0, <= 4.1.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2022-40199: 1.19% estimated exploitation activity in the next 30 days; percentile 68.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-wjpv-frf2-3r58

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-40199

Advisory: EC-CUBE Directory traversal vulnerability
IDs: CVE-2022-40199, GHSA-wjpv-frf2-3r58
Record: https://patchnext.com/advisories/cve-2022-40199 (revision 1, source checked 26 Oct 2026, 14:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ec-cube/ec-cube: affected >= 3.0.0, <= 3.0.18-p4; >= 4.0.0, <= 4.1.2

## Suggested inspection (read-only)
- Packagist ec-cube/ec-cube: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ec-cube/ec-cube.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wjpv-frf2-3r58 (GitHub-reviewed advisory GHSA-wjpv-frf2-3r58 lists affected ranges: Packagist ec-cube/ec-cube >=3.0.0 =4.0.0 <=4.1.2)

Commands are suggestions: review each one before running it.

Loading voting…