Magento Improper Authorization vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-39418: 0.41% estimated exploitation activity in the next 30 days; percentile 35.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Magento 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 vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures to view and edit low-sensitivity information. Exploitation of this issue does not require user interaction.

Published by the source

14 Aug 2024, 12:35 UTC

Last modified by the source

6 Nov 2025, 16:49 UTC

Source last checked

26 Oct 2026, 14:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gvgf-pvh5-vjh4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-39418

Advisory: Magento Improper Authorization vulnerability
IDs: CVE-2024-39418, GHSA-gvgf-pvh5-vjh4
Record: https://patchnext.com/advisories/cve-2024-39418 (revision 1, source checked 26 Oct 2026, 14:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: magento/community-edition 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist magento/project-community-edition: affected <= 2.0.2
- Packagist magento/community-edition: affected >= 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-p1, < 2.4.4-p10; >= 2.4.7, <= 2.4.7; >= 2.4.6, <= 2.4.6; >= 2.4.5, <= 2.4.5; >= 2.4.4, <= 2.4.4; fixed in 2.4.7-p2, 2.4.4-p10, 2.4.6-p7, 2.4.5-p9

## Suggested inspection (read-only)
- Packagist magento/project-community-edition: check the installed version with your package manager.
- Packagist magento/community-edition: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on magento/project-community-edition, magento/community-edition.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gvgf-pvh5-vjh4 (GitHub-reviewed advisory GHSA-gvgf-pvh5-vjh4 lists affected ranges: Packagist magento/project-community-edition >=0 =2.4.7-beta1 =2.4.6-p1 =2.4.5-p1 =2.4.4-p1 =2.4.7 =2.4.6 =2.4.5 =2.4.4 <=2.4.4)

Commands are suggestions: review each one before running it.