Advisory record · GHSA-qm77-mqf3-fmhq

Magento Improper Authorization leads to security feature bypass

CVSS 4.3 MediumEPSS 0.0044 · 39th percentile

Published by the GitHub Advisory Database at 14 Aug 2024, 12:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
magento/project-community-editionPackagist<=2.0.2No fixed version yet
magento/community-editionPackagist>=2.4.7-beta1, <2.4.7-p2 || >=2.4.6-p1, <2.4.6-p7 || >=2.4.5-p1, <2.4.5-p9 || <2.4.4-p10 || =2.4.4 || =2.4.5 || =2.4.6 || =2.4.72.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10
Identifiers
GHSA-qm77-mqf3-fmhq · CVE-2024-39411 · PKSA-4jrq-qp4c-nqw3 · PKSA-9h42-hjp4-8jwg
Weakness (CWE)
CWE-285
Published
14 Aug 2024
Updated
23 Oct 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Magento (magento/community-edition and magento/project-community-edition) versions 2.4.7-p1, 2.4.6-p6, 2.4.5-p8, 2.4.4-p9 and earlier are affected by an improper authorization flaw that allows a security feature bypass. A low-privileged attacker can exploit it without user interaction to disclose minor information. Upgrade magento/community-edition to 2.4.4-p10, 2.4.5-p9, 2.4.6-p7, 2.4.7-p2 or later; no fixed version is listed for magento/project-community-edition.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (adobe)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 39th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:26 UTC First seen by agentprime
  2. 31 Oct 2026, 14:26 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.