dbcve.org
MagentoCMS

CVE-2020-24401

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-09
Fix available
A fix is available. Upgrade to 2.3.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Magento fails to properly revoke user session permissions when an administrator removes the user's role or disables the account. The system continues to honor cached session tokens with the old role permissions, allowing unauthorized access to resources that should no longer be accessible after role removal or account disablement.

MitigationApply the relevant Magento security patch (SUPEE-11219 or 2.4.1/2.3.5p2) which implements proper session invalidation when roles are modified or accounts are disabled. Review and manually invalidate existing user sessions after applying the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MagentoCMS
Affected:< 2.3.5= 2.3.5= 2.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Magento version
    Run the command `php bin/magento --version` or check the `composer.json` file in the Magento root directory for the version number
    Affected if The installed version is 2.4.0 or 2.3.5 or any version below 2.3.5 (such as 2.3.4, 2.3.3, etc.)
  2. Verify session invalidation logic after role removal
    Create a test admin user, assign a role with specific permissions, establish a valid session, then remove the user's role via admin panel, and attempt to use the existing session token to access protected resources
    Affected if The old session token still grants access to resources after the role has been removed from the user account
  3. Verify session invalidation logic after account disablement
    Create a test admin user, establish a valid session, then disable the user account via admin panel, and attempt to use the existing session token to access protected resources
    Affected if The old session token still grants access to resources after the account has been disabled
  4. Review admin session handling configuration
    Check the admin session configuration in `app/etc/env.php` or the adminhtml session settings in the Magento configuration. Look for settings related to session lifetime and validation.
    Affected if Session lifetime is set to an excessively long period (several hours or days) and no session invalidation occurs when user roles change
  5. Check for presence of security patch SUPEE-11219
    Review the codebase for the presence of fixes related to session invalidation in files such as `Magento\User\Model\User.php` or `Magento\Security\Model\ResourceModel\UserSession.php`. Search for code that handles role change events and invalidates associated sessions.
    Affected if The codebase does not contain session invalidation logic when user roles are modified or when user accounts are disabled

A user is affected if their Magento installation version is 2.4.0, 2.3.5, or any version below 2.3.5, and testing confirms that sessions remain valid after role removal or account disablement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 2.3.5 or later
Fixed in 2.3.5
Interim mitigation

Apply the relevant Magento security patch (SUPEE-11219 or 2.4.1/2.3.5p2) which implements proper session invalidation when roles are modified or accounts are disabled. Review and manually invalidate existing user sessions after applying the patch.

Fix this in Magento Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-24401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-24401 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data