GHSA-r8vh-cm9f-rc29 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in dweeves/magmi. 2 public exploit references exist, so weaponization risk is real. A fix is available for dweeves/magmi — see the affected versions and patch details below.
Magmi XSS Vulnerability
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-r8vh-cm9f-rc29 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 377,333 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
dweeves/magmiReal-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
A Cross-Site Scripting (XSS) was discovered in Magmi 0.7.22. The vulnerability exists due to insufficient filtration of user-supplied data (prefix) passed to the magmi-git-master/magmi/web/ajax_gettime.php URL. An attacker could execute arbitrary HTML and script code in a browser in the context of the vulnerable website.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | dweeves/magmi | all versions | 0.7.24composer require dweeves/magmi:^0.7.24 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dweeves/magmi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dweeves/magmi to 0.7.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r8vh-cm9f-rc29 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-r8vh-cm9f-rc29 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r8vh-cm9f-rc29. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-r8vh-cm9f-rc29
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-r8vh-cm9f-rc29 -u https://target- Template
- Magmi 0.7.22 - Cross-Site Scripting
- Severity
- medium
- Impact
- Successful exploitation of this vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the victim's browser, leading to session hijacking, defacement, or theft of sensitive information.
- Remediation
- Upgrade to a patched version of Magmi or apply the necessary security patches to mitigate the XSS vulnerability.
Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-r8vh-cm9f-rc29 in your dependencies?
O3 Security finds GHSA-r8vh-cm9f-rc29 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.