How severe is CVE-2017-7391?

CVE-2017-7391 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-7391?

CVE-2017-7391 affects the following packages: dweeves/magmi (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-7391?

Update dweeves/magmi to 0.7.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7391 is resolved across your whole dependency graph.

How do I detect CVE-2017-7391 in my Packagist dependencies?

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.

How do I mitigate CVE-2017-7391 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2017-7391 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2017-7391, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-7391?

CVE-2017-7391 has an EPSS (Exploit Prediction Scoring System) score of 8.3%, placing it in the 95th 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.

What type of vulnerability is CVE-2017-7391?

CVE-2017-7391 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2017-7391?

A Nuclei detection template exists for CVE-2017-7391, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-7391 published, and has it been updated?

CVE-2017-7391 was published on April 1, 2017 and was last updated on October 20, 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

Not in CISA KEV

MEDIUM severity

CVE-2017-7391 — magmi

MEDIUMFix: dweeves/magmi-git#525

CVE-2017-7391 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in dweeves/magmi. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for dweeves/magmi — see the affected versions and patch details below.

Magmi XSS Vulnerability

Also known asGHSA-r8vh-cm9f-rc29

Published

Apr 1, 2017

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

8.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘dweeves/magmi

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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dweeves/magmi`	all versions	0.7.24`composer require dweeves/magmi:^0.7.24`

Affected Products

1 product · 1 configurations

Application

magmimagmi_project

1 version

0.7.22

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A Cross-Site Scripting (XSS) was discovered in 'Magmi 0.7.22'. The vulne…

zdnet.comAPIMay 2020

Report on documentcloud.org

documentcloud.orgAPIMay 2020

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2017-7391 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

How to detect CVE-2017-7391

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2017-7391 -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

O3 Security · Impact-Aware SCA

Is CVE-2017-7391 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

OpenSSF Scorecard

Package health score

magmi-git

2.6/10

Maintained0/10

Code-Review4/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Apr 1, 2017

First exploit

May 18, 2020

Last updated

Oct 20, 2026

Identifiers

CVE-2017-7391

GHSA-r8vh-cm9f-rc29

References

Advisorynvd.nist.gov · CVE 2017 7391 Fixgithub.com Fixgithub.com Websecurityfocus.com Webgithub.com · a9566b141b58bf40a9dd904a74e6efcc225a28a3 Webweb.archive.org

Related vulnerabilities

Also affects dweeves/magmi

This CVE is medium severity; 5 of 5 other CVEs affecting dweeves/magmi are rated as high or higher (top: critical).

CVE-2014-8770CVE-2015-2068CVE-2015-2067CVE-2020-5776CVE-2020-5777

Same weakness: CWE-79

This CVE is medium severity; 3 of 3 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-113787CVE-2026-44267CVE-2026-96632Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026