Skip to content

Magento does not properly protect credentials

Low severity GitHub Reviewed Published Apr 8, 2025 to the GitHub Advisory Database • Updated Oct 23, 2025

Package

composer magento/community-edition (Composer)

Affected versions

>= 2.4.7-beta1, < 2.4.7-p5
>= 2.4.6-p1, < 2.4.6-p10
>= 2.4.5-p1, < 2.4.5-p12
< 2.4.4-p13
>= 2.4.8-beta1, < 2.4.8-beta2
= 2.4.5
= 2.4.4
= 2.4.6
= 2.4.7

Patched versions

2.4.7-p5
2.4.6-p10
2.4.5-p12
2.4.4-p13
2.4.8-beta2
composer magento/project-community-edition (Composer)
<= 2.0.2
None

Description

Magento versions 2.4.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12, 2.4.8-beta2 and earlier are affected by an Insufficiently Protected Credentials vulnerability that could lead to a security feature bypass. A high privileged attacker could exploit this vulnerability to gain unauthorized access to protected resources by obtaining sensitive credential information. Exploitation of this issue does not require user interaction.

References

Published by the National Vulnerability Database Apr 8, 2025
Published to the GitHub Advisory Database Apr 8, 2025
Reviewed Oct 23, 2025
Last updated Oct 23, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(26th percentile)

Weaknesses

Insufficiently Protected Credentials

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. Learn more on MITRE.

CVE ID

CVE-2025-27192

GHSA ID

GHSA-2r94-wm5v-4prx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.