cve.bz

CVE-2020-9689 magento magento: Path traversal

6.5 mediumEPSS 4.1%Fix available

Medium (6.5) in magento magento. EPSS 4.1% estimated probability of exploitation activity in the next 30 days. Fixed in magento/community-edition 2.3.5-p2.

On this page
Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have a path traversal vulnerability. Successful exploitation could lead to arbitrary code execution.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
EPSS
4.1% (unchanged from 4.1% a week ago; 4.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-9689 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-9689?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-9689?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-9689 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
magento:magentobefore 2.3.5
magento:magento2.3.5
magento:magento2.3.5:p1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fr6f-xmfx-rrpqPackagistmagento/community-edition<2.3.5-p22.3.5-p2
GHSA-fr6f-xmfx-rrpqPackagistmagento/project-community-edition<=2.0.2no fix published

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON