LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24404: Incorrect permissions in Integrations component could lead to unauthorized deletion of cmsPages via REST API

Magento version 2.4.0 and 2.3.5p1 (and earlier) are affected by an incorrect permissions vulnerability within the Integrations component. This vulnerability could be abused by users with permissions to the Pages resource to delete cms pages via the REST API without authorization.

LowCVSS 2.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity Magento Commerce authorization flaw. A highly privileged user who already has Pages permissions could use the REST API to delete CMS pages without proper authorization. The main business risk is unauthorized content removal, not data theft or system takeover.

Executive priority

Handle in normal patch governance unless CMS integrity is business-critical. Prioritize systems with many administrators, external integrations, or exposed admin/API surfaces.

Technical view

CVE-2020-24404 is a CWE-285 incorrect permissions issue in Magento's Integrations component affecting Magento Commerce 2.4.0, 2.3.5-p1, and earlier. CVSS 3.1 is 2.7: network reachable, low complexity, high privileges required, no user interaction, and limited integrity impact.

Likely exposure

Exposure is most relevant for Magento Commerce sites on 2.4.0, 2.3.5-p1, or earlier where REST API access and users or integrations with Pages permissions exist.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation evidence. Abuse requires high privileges and appears limited to deleting CMS pages through REST API authorization gaps.

Researcher notes

The issue is authorization-bound, not unauthenticated remote compromise. The source bundle does not provide exploit details or a named fixed version, so validation should focus on version exposure, role permissions, API logs, and Adobe advisory status.

Mitigation direction

  • Identify Magento Commerce instances running affected versions.
  • Review Adobe APSB20-59 for the vendor-approved update or remediation path.
  • Restrict REST API access to trusted administrative networks where feasible.
  • Review users and integrations granted Pages permissions.
  • Monitor for unexpected CMS page deletion events.

Validation and detection

  • Confirm each Magento Commerce instance version against affected versions.
  • List users and integrations with Pages resource permissions.
  • Review API and admin logs for unexpected CMS page deletion activity.
  • Verify Adobe guidance from APSB20-59 has been applied.
  • Confirm CMS page deletion requires intended authorization after remediation.
Prepared
Confidence
high
Sources
3

Public sources used

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 · low confidence lookup

CWE-285: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-24404 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:N/I:L/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
2.7CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N1.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

CWE-285 · source CWE mapping

Improper Authorization

Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs