LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24401: Incorrect permissions following the deletion of a user role or deactivation of a user

Magento versions 2.4.0 and 2.3.5p1 (and earlier) are affected by an incorrect authorization vulnerability. A user can still access resources provisioned under their old role after an administrator removes the role or disables the user's account.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-24401 means a former or disabled Magento user may keep access they should have lost. The business risk is unauthorized access to sensitive commerce administration or data after an account or role change. It is not listed as known exploited in the provided sources.

Executive priority

Treat as a governance and insider-risk issue for Magento environments. It is not a critical internet-wide emergency based on the provided evidence, but affected commerce platforms should be updated and audited because confidentiality and integrity impacts are high.

Technical view

Magento Commerce 2.4.0, 2.3.5-p1, and earlier are affected by incorrect authorization, CWE-863. After an administrator deletes a role or disables a user, access to resources provisioned under the prior role may remain available. CVSS 3.1 is 6.5 with high confidentiality and integrity impact, requiring high privileges.

Likely exposure

Exposure is limited to affected Magento Commerce deployments, especially environments with active staff turnover, role cleanup, or disabled administrative users. Systems with reachable admin or management surfaces have higher practical risk.

Exploitation context

The source bundle does not identify active exploitation, public exploit use, or CISA KEV listing. Abuse appears to require an existing or formerly authorized user context, making insider misuse or compromised privileged accounts the main concern.

Researcher notes

Evidence is concise and points to an authorization state issue after account or role lifecycle changes. The bundle does not include root cause, exploit details, fixed version names, or workaround specifics beyond Adobe’s advisory reference.

Mitigation direction

  • Review Adobe APSB20-59 for vendor-designated fixed versions and upgrade guidance.
  • Prioritize affected Magento Commerce 2.4.0, 2.3.5-p1, and earlier deployments.
  • Audit disabled users and deleted roles for unintended remaining access.
  • Restrict administrative access to trusted networks and authenticated administrators.
  • Review access governance around role changes and account deactivation.

Validation and detection

  • Inventory Magento Commerce versions across production and staging.
  • Confirm whether any deployment runs 2.4.0, 2.3.5-p1, or earlier.
  • Review logs for access after user deactivation or role removal.
  • Verify disabled users cannot access previously assigned resources.
  • Check role deletion workflows for residual authorization behavior.
Prepared
Confidence
medium
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-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-24401 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
6.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

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

Incorrect Authorization

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