Io.jenkins.plugins:xooa: Jenkins Xooa Plugin vulnerability exposes unencrypted tokens to authenticated users
Affects io.jenkins.plugins:xooaSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 4 Nov 2026, 18:15 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenio.jenkins.plugins:xooa | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should restrict file system access to the Jenkins controller to trusted administrators only to prevent unauthorized viewing of the token. Monitor vendor advisories for any forthcoming patches or updates addressing this issue.
Description
Jenkins Xooa Plugin versions 0.0.7 and earlier store the Xooa Deployment Token unencrypted in the global configuration file on the Jenkins controller. This token can be accessed by any user with file system access to the Jenkins controller, potentially exposing sensitive credentials.