GHSA-x63v-prhc-xx6f — ownership
HIGHGHSA-x63v-prhc-xx6f is a high-severity (CVSS 8) Cross-site Scripting (XSS) vulnerability in com.synopsys.jenkinsci:ownership. No vendor fix is recorded yet; mitigation options are listed below.
Stored Cross-site Scripting vulnerability in Jenkins Job and Node ownership 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-x63v-prhc-xx6f 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
com.synopsys.jenkinsci:ownershipReal-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
Jenkins Job and Node ownership Plugin 0.13.0 and earlier does not escape the names of the secondary owners, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.synopsys.jenkinsci:ownership | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.synopsys.jenkinsci:ownership, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of com.synopsys.jenkinsci:ownership has shipped for GHSA-x63v-prhc-xx6f yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-x63v-prhc-xx6f can be triaged on real exposure rather than presence alone.
Tailored to GHSA-x63v-prhc-xx6f. 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-x63v-prhc-xx6f in your dependencies?
O3 Security finds GHSA-x63v-prhc-xx6f across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.