LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24406: Document root path disclosure on Maintenance page

When in maintenance mode, Magento version 2.4.0 and 2.3.4 (and earlier) are affected by an information disclosure vulnerability that could expose the installation path during build deployments. This information could be helpful to attackers if they are able to identify other exploitable vulnerabilities in the environment.

LowCVSS 3.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2020-24406 is a low-severity Magento information disclosure issue. During build deployments, a site in maintenance mode may reveal its installation path. That path alone is not a compromise, but it can help attackers understand the environment if another vulnerability is present.

Executive priority

Treat this as a hygiene and hardening item, not an emergency. Prioritize remediation during normal patch cycles, especially for internet-facing Magento stores or environments with frequent public maintenance windows.

Technical view

Magento Commerce 2.4.0, 2.3.4, and earlier are reported affected. The issue is CWE-200 information disclosure with CVSS 3.1 score 3.7: network reachable, high attack complexity, no privileges, no user interaction, low confidentiality impact only.

Likely exposure

Exposure is most likely on Magento Commerce sites that enter publicly reachable maintenance mode during build deployments. The bundle does not identify affected configurations beyond versions 2.4.0, 2.3.4, and earlier.

Exploitation context

The source bundle does not report active exploitation, and CISA KEV status is false. The disclosed document root path is mainly useful for reconnaissance and would usually matter more when combined with another exploitable weakness.

Researcher notes

Evidence is limited to the CVE record and Adobe advisory reference. The bundle names no exploit, no specific fixed version, and no standalone workaround. Analysis should stay scoped to path disclosure during maintenance-mode build deployments.

Mitigation direction

  • Review Adobe APSB20-59 and apply applicable Magento security updates.
  • Inventory Magento Commerce instances at 2.4.0, 2.3.4, or earlier.
  • Reduce public exposure of maintenance pages during deployment windows where feasible.
  • Check vendor guidance before assuming a standalone workaround exists.

Validation and detection

  • Confirm Magento Commerce versions across production and staging environments.
  • Review deployment workflows for public maintenance mode exposure.
  • Inspect maintenance page behavior defensively for installation path disclosure.
  • Check vulnerability management records for APSB20-59 remediation status.
Prepared
Confidence
high
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-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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
cve · low confidence lookup

CVE-2020-24406 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
3.7 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2020-24406Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
AdobeMagento Commerceunspecified, unspecified, unspecifiedListed
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.