CVE Tools

CVE-2025-49594

XWiki OIDC Authenticator vulnerable to creation of token for any user with just `view` right

No known exploitation. EPSS puts it in the 37th percentile. Fixed in 2.18.2.

Published Updated Sources: CVE.org, NVD, GitHub, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Xwiki-contrib OidcAffected: >= 2.17.1, < 2.18.2Upgrade to: not statedStated by: CVE record
  • Maven org.xwiki.contrib.oidc:oidc-authenticatorAffected: ≥ 2.17.1, < 2.18.2Upgrade to: 2.18.2Stated by: GitHub advisory
  • Сообщество свободного программного обеспечения XWiki OIDCAffected: от 2.17.1 до 2.18.2Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

XWiki OIDC Authenticator: Users with "view" access can create tokens for any users they can view

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS37th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 37th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 368 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Publishedweakness classified

Affected products

Technical detail

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by bdu.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity LowNo special conditions required

Impact if exploited

  • Confidentiality H
  • Integrity H
  • Availability H

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Maven, not every advisory.