CVE-2017-6484 — inter-mediator
MEDIUMCVE-2017-6484 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in inter-mediator/inter-mediator. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for inter-mediator/inter-mediator — see the affected versions and patch details below.
INTER-Mediator Cross-Site Scripting (XSS)
EPSS Exploitation Probability
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
inter-mediator/inter-mediatorReal-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
Multiple Cross-Site Scripting (XSS) issues were discovered in INTER-Mediator 5.5. The vulnerabilities exist due to insufficient filtration of user-supplied data (c and cred) passed to the "INTER-Mediator-master/Auth_Support/PasswordReset/resetpassword.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 | inter-mediator/inter-mediator | ≥ 5.5&&< 5.6 | 5.6composer require inter-mediator/inter-mediator:^5.6 |
Affected Products
inter-mediatorinter-mediatorResearch 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 inter-mediator/inter-mediator, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update inter-mediator/inter-mediator to 5.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-6484 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.
Frequently Asked Questions
Is CVE-2017-6484 in your dependencies?
Find it across Packagist, including transitive dependencies.