Summary
XWiki OIDC Authenticator: Users with "view" access can create tokens for any users they can view
Workarounds
The only workaround is to disable token access.
References
- https://jira.xwiki.org/browse/OIDC-240
- https://github.com/xwiki-contrib/oidc/commit/d90d717172283aaa96bb5bb44e357f910ae64adb
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Impact
Anyone with VIEW access to a user profile can create a token for that user. If that XWiki instance is configured to allow token authentication, it allows authentication with any user (since users are very commonly viewable, at least to other registered users).
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Version 2.18.2.
Frequently Asked Questions
- What is CVE-2025-49594? CVE-2025-49594 is a critical-severity security vulnerability in org.xwiki.contrib.oidc:oidc-authenticator (maven), affecting versions >= 2.17.1, < 2.18.2. It is fixed in 2.18.2.
- Which versions of org.xwiki.contrib.oidc:oidc-authenticator are affected by CVE-2025-49594? org.xwiki.contrib.oidc:oidc-authenticator (maven) versions >= 2.17.1, < 2.18.2 is affected.
- Is there a fix for CVE-2025-49594? Yes. CVE-2025-49594 is fixed in 2.18.2. Upgrade to this version or later.
- Is CVE-2025-49594 exploitable, and should I be worried? Whether CVE-2025-49594 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-49594 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-49594? Upgrade
org.xwiki.contrib.oidc:oidc-authenticatorto 2.18.2 or later.