Jenkins WSO2 OAuth vulnerabilities
5 CVEs affecting Jenkins WSO2 OAuth, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2025-47889, published 2025-05-14.
More from Jenkins.
Highest priority
Known exploited (CISA KEV) first, then by EPSS exploit probability.
- CVE-2025-47889, published 2025-05-14. Critical severity, CVSS 9.8. EPSS: 0.6% chance of exploitation in the next 30 days. In Jenkins WSO2 Oauth Plugin 1.0 and earlier, authentication claims are accepted without validation by the "WSO2 Oauth" security realm, allowing unauthenticated attackers to log in to controllers…
- CVE-2023-33005, published 2023-05-16. Medium severity, CVSS 5.4. EPSS: 0.4% chance of exploitation in the next 30 days. Jenkins WSO2 Oauth Plugin 1.0 and earlier does not invalidate the previous session on login.
- CVE-2023-30528, published 2023-04-12. Medium severity, CVSS 6.5. EPSS: 0.4% chance of exploitation in the next 30 days. Jenkins WSO2 Oauth Plugin 1.0 and earlier does not mask the WSO2 Oauth client secret on the global configuration form, increasing the potential for attackers to observe and capture it.
- CVE-2023-30527, published 2023-04-12. Medium severity, CVSS 4.3. EPSS: 0.3% chance of exploitation in the next 30 days. Jenkins WSO2 Oauth Plugin 1.0 and earlier stores the WSO2 Oauth client secret unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by users with access to the…
- CVE-2023-33006, published 2023-05-16. Medium severity, CVSS 5.4. EPSS: 0.3% chance of exploitation in the next 30 days. A cross-site request forgery (CSRF) vulnerability in Jenkins WSO2 Oauth Plugin 1.0 and earlier allows attackers to trick users into logging in to the attacker's account.