LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24402: Incorrect permissions in the Integrations component could lead to unauthorized deletion of customer details via REST API

Magento version 2.4.0 and 2.3.5p1 (and earlier) are affected by an incorrect permissions vulnerability in the Integrations component. This vulnerability could be abused by authenticated users with permissions to the Resource Access API to delete customer details via the REST API without authorization.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw could let a highly privileged authenticated Magento Commerce user or integration delete customer details through the REST API without proper authorization. It is not a broad unauthenticated compromise, but it can damage customer records and business operations if risky integration permissions exist.

Executive priority

Treat as a moderate-priority integrity risk for affected Magento Commerce stores. Prioritize if customer data operations depend on third-party integrations or many privileged API accounts exist, because the business impact is unauthorized deletion rather than data theft or full system takeover.

Technical view

CVE-2020-24402 is a CWE-276 incorrect-permissions issue in Magento Commerce Integrations. Adobe-listed affected versions include Magento 2.4.0, 2.3.5-p1, and earlier. Abuse requires authenticated access with Resource Access API permissions and impacts integrity by enabling unauthorized customer-detail deletion via REST API.

Likely exposure

Exposure is most likely in Magento Commerce deployments on 2.4.0, 2.3.5-p1, or earlier where users or integrations have Resource Access API permissions. The source bundle does not identify unauthenticated exposure or other affected Adobe products.

Exploitation context

The CVSS vector shows network reachability, low complexity, high privileges required, and no user interaction. The source bundle marks CISA KEV as false and provides no evidence of active exploitation or public weaponization.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE-276 classification, affected Magento Commerce versions, and Adobe bulletin reference. Do not assume exploitation in the wild, unauthenticated access, or fixed-version details beyond what Adobe APSB20-59 confirms.

Mitigation direction

  • Check Adobe APSB20-59 and apply the vendor-recommended Magento security update for affected versions.
  • Inventory Magento Commerce versions and prioritize systems at 2.4.0, 2.3.5-p1, or earlier.
  • Review integrations and users with Resource Access API permissions for least-privilege scope.
  • Remove unused integrations and unnecessary REST API permissions.
  • Ensure backups and recovery procedures cover customer record deletion scenarios.

Validation and detection

  • Confirm deployed Magento Commerce versions against the affected versions in the CVE record.
  • List users and integrations granted Resource Access API permissions.
  • Review audit logs for unexpected customer deletion activity through REST API paths.
  • Verify vendor security guidance or update status from Adobe APSB20-59.
  • Test that non-authorized integration roles cannot delete customer details.
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 · low confidence lookup

CWE-276: 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-24402 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
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2020-24402Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Incorrect Default Permissions

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