CVE-2025-27192: Magento does not properly protect credentials

CVE-2025-27192 · Severity: low · CVSS 3.1 · Published 2025-04-08

Magento does not properly protect credentials

Technologies: magento/community-edition (Packagist), magento/project-community-edition (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2025-27192 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-27192 being exploited in the wild.
How severe is CVE-2025-27192?
Low severity, with a CVSS score of 3.1, published 8 April 2025.
Which products and versions are affected?
magento/community-edition (Packagist) ECOSYSTEM:introduced=2.4.7-beta1,fixed=2.4.7-p5; magento/project-community-edition (Packagist) ECOSYSTEM:introduced=0,last_affected=2.0.2.
Is there a fix for CVE-2025-27192?
Yes. magento/community-edition (Packagist): upgrade to 2.4.7-p5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-27192?
Check whether you run magento/community-edition (Packagist) or magento/project-community-edition (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • magento/community-edition (Packagist): upgrade to 2.4.7-p5 or later
    composer require magento/community-edition:^2.4.7-p5

Affected products

  • magento/community-edition (Packagist) ECOSYSTEM:introduced=2.4.7-beta1,fixed=2.4.7-p5
  • magento/project-community-edition (Packagist) ECOSYSTEM:introduced=0,last_affected=2.0.2

Identifiers

  • CVE-2025-27192
  • GHSA-2r94-wm5v-4prx

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.