GHSA-5x89-75r7-8rjh — usemango-runner
MEDIUMGHSA-5x89-75r7-8rjh is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in it.infuse.jenkins:usemango-runner. A fix is available for it.infuse.jenkins:usemango-runner — see the affected versions and patch details below.
XSS vulnerability in Jenkins useMango Runner Plugin
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-5x89-75r7-8rjh 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,166 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
it.infuse.jenkins:usemango-runnerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Multiple form validation endpoints in useMango Runner Plugin 1.4 and earlier do not escape values received from the useMango service.
This results in a cross-site scripting (XSS) vulnerability exploitable by users able to control the values returned from the useMango service.
useMango Runner Plugin 1.5 escapes all values received from the useMango service in form validation messages.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | it.infuse.jenkins:usemango-runner | all versions | 1.5it.infuse.jenkins:usemango-runner:1.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for it.infuse.jenkins:usemango-runner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update it.infuse.jenkins:usemango-runner to 1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5x89-75r7-8rjh 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-5x89-75r7-8rjh can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5x89-75r7-8rjh. 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-5x89-75r7-8rjh in your dependencies?
O3 Security finds GHSA-5x89-75r7-8rjh across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.