Wso2 OauthApplication · Jenkins
CVE-2025-47889
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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 using this security realm using any username and any password, including usernames that do not exist.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins WSO2 Oauth Plugin 1.0 and earlier has a critical authentication bypass vulnerability in its 'WSO2 Oauth' security realm. The plugin accepts authentication claims without any validation, allowing unauthenticated attackers to authenticate using any username and any password, including non-existent usernames. This completely defeats the authentication mechanism for any Jenkins controller using this plugin as its security realm.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wso2 OauthApplication
<= 1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WSO2 Oauth plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'wso2' or 'WSO2 Oauth' in the plugin listAffected if The plugin appears in the installed plugins list with name containing 'wso2' or 'WSO2 Oauth' and version 1.0 or earlier
-
Confirm WSO2 Oauth is the active security realmNavigate to Manage Jenkins > Configure Global Security > Security Realm section and inspect which security realm is selectedAffected if The 'WSO2 Oauth' option is selected as the Security Realm
-
Check the exact plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, locate the WSO2 Oauth plugin and note the version number displayedAffected if The installed version is 1.0 or any version lower than 1.0 (e.g., 0.9, 0.8, etc.)
-
Verify external authentication is reachableAttempt to access the WSO2 Oauth endpoint or verify network connectivity to the configured WSO2 Identity ServerAffected if The WSO2 Identity Server is reachable and the plugin is configured to use it for authentication
A defender is affected if the WSO2 Oauth plugin version 1.0 or earlier is installed AND configured as the active security realm in Jenkins global security settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately disable the WSO2 Oauth security realm and switch to an alternative authentication method. If an updated version of the plugin is available, apply the update after validating the fix through testing in a non-production environment.
Fix this in Wso2 Oauth
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data