How severe is GHSA-5j2g-3ph4-rgvm?

GHSA-5j2g-3ph4-rgvm has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-5j2g-3ph4-rgvm?

GHSA-5j2g-3ph4-rgvm affects the following packages: openmage/magento-lts (Packagist), openmage/magento-lts (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5j2g-3ph4-rgvm?

Update openmage/magento-lts to 19.4.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j2g-3ph4-rgvm is resolved across your whole dependency graph.

How do I detect GHSA-5j2g-3ph4-rgvm in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5j2g-3ph4-rgvm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5j2g-3ph4-rgvm?

O3 pinpoints whether GHSA-5j2g-3ph4-rgvm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5j2g-3ph4-rgvm actively exploited in the wild?

No public exploit code has been indexed for GHSA-5j2g-3ph4-rgvm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5j2g-3ph4-rgvm?

GHSA-5j2g-3ph4-rgvm has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-5j2g-3ph4-rgvm published, and has it been updated?

GHSA-5j2g-3ph4-rgvm was published on January 27, 2023 and was last updated on March 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-5j2g-3ph4-rgvm

HIGH

Fix for authenticated remote code execution through layout update

Also known asCVE-2021-41144

Published

Jan 27, 2023

Updated

Mar 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk63th percentile+0.57%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐘openmage/magento-lts🐘openmage/magento-lts

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A layout block was able to bypass the block blacklist to execute remote code.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`openmage/magento-lts`	all versions	19.4.22
🐘Packagist	`openmage/magento-lts`	≥ 20.0.0&&< 20.0.19	20.0.19

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openmage/magento-lts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openmage/magento-lts to 19.4.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j2g-3ph4-rgvm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-5j2g-3ph4-rgvm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5j2g-3ph4-rgvm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A layout block was able to bypass the block blacklist to execute remote code.

O3 Security · Impact-Aware SCA

Is GHSA-5j2g-3ph4-rgvm in your dependencies?

O3 detects GHSA-5j2g-3ph4-rgvm across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works