GHSA-xjm6-jfmg-qc6p is a medium-severity (CVSS 5.5) CWE-270 vulnerability in aimeos/aimeos-core. A fix is available for aimeos/aimeos-core — see the affected versions and patch details below.
Aimeos denial of service vulnerability in SaaS and marketplace setups
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xjm6-jfmg-qc6p.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-xjm6-jfmg-qc6p plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
aimeos/aimeos-core🐘aimeos/aimeos-core🐘aimeos/aimeos-coreReal-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
Aimeos is an Open Source e-commerce framework for online shops. All SaaS and marketplace setups using Aimeos version from 2022/2023/2024 are affected by a potential denial of service attack. Users should upgrade to versions 2022.10.17, 2023.10.17, or 2024.04 of the aimeos/aimeos-core package to receive a patch.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | aimeos/aimeos-core | ≥ 2024.04.1&&< 2024.04.7 | 2024.04.7composer require aimeos/aimeos-core:^2024.04.7 |
| 🐘Packagist | aimeos/aimeos-core | ≥ 2023.04.1&&< 2023.10.17 | 2023.10.17composer require aimeos/aimeos-core:^2023.10.17 |
| 🐘Packagist | aimeos/aimeos-core | ≥ 2022.04.1&&< 2022.10.17 | 2022.10.17composer require aimeos/aimeos-core:^2022.10.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/aimeos-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aimeos/aimeos-core to 2024.04.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjm6-jfmg-qc6p 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xjm6-jfmg-qc6p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xjm6-jfmg-qc6p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xjm6-jfmg-qc6p in your dependencies?
O3 Security finds GHSA-xjm6-jfmg-qc6p across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.