Skip to content

Magento LTS vulnerable to stored XSS in theme config fields

Low severity GitHub Reviewed Published Feb 28, 2025 in OpenMage/magento-lts • Updated Mar 3, 2025

Package

composer openmage/magento-lts (Composer)

Affected versions

< 20.12.3

Patched versions

20.12.3

Description

As reported by Aakash Adhikari, Github: @justlife4x4, the Design > Themes > Skin (Images / CSS) config field allows a Stored XSS when it contains an end script tag.

Impact

A malicious user with access to this configuration field could use a Stored XSS to affect other authenticated admin users in the admin panel.

The attack requires an admin user with configuration access, so in practice, it is not very likely to be used for gaining elevated privileges, although it could theoretically be used to impersonate other users.

image

References

@colinmollenhour colinmollenhour published to OpenMage/magento-lts Feb 28, 2025
Published by the National Vulnerability Database Feb 28, 2025
Published to the GitHub Advisory Database Mar 3, 2025
Reviewed Mar 3, 2025
Last updated Mar 3, 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
Adjacent
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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:A/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:L

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.
(18th percentile)

Weaknesses

CVE ID

CVE-2025-27400

GHSA ID

GHSA-5pxh-89cx-4668

Source code

Credits

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