How severe is GHSA-f9c6-2f9p-82jj?

No CVSS score has been assigned to GHSA-f9c6-2f9p-82jj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f9c6-2f9p-82jj?

GHSA-f9c6-2f9p-82jj affects the following packages: org.xwiki.platform:xwiki-platform-security-authentication-ui (Maven), org.xwiki.platform:xwiki-platform-security-authentication-ui (Maven), org.xwiki.platform:xwiki-platform-security-authentication-ui (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f9c6-2f9p-82jj?

Update org.xwiki.platform:xwiki-platform-security-authentication-ui to 15.10.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9c6-2f9p-82jj is resolved across your whole dependency graph.

How do I detect GHSA-f9c6-2f9p-82jj in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-security-authentication-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f9c6-2f9p-82jj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f9c6-2f9p-82jj?

O3 pinpoints whether GHSA-f9c6-2f9p-82jj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f9c6-2f9p-82jj actively exploited in the wild?

No public exploit code has been indexed for GHSA-f9c6-2f9p-82jj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-f9c6-2f9p-82jj?

GHSA-f9c6-2f9p-82jj has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-f9c6-2f9p-82jj?

GHSA-f9c6-2f9p-82jj is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f9c6-2f9p-82jj published, and has it been updated?

GHSA-f9c6-2f9p-82jj was published on April 30, 2025 and was last updated on May 1, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-f9c6-2f9p-82jj

Any user with view access to the XWiki space can change the authenticator

Also known asCVE-2025-46557

Published

Apr 30, 2025

Updated

May 1, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk38th percentile+0.11%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-security-authentication-ui☕org.xwiki.platform:xwiki-platform-security-authentication-ui☕org.xwiki.platform:xwiki-platform-security-authentication-ui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A user who can access pages located in the XWiki space (by default, anyone) can access the page XWiki.Authentication.Administration and (unless an authenticator is set in xwiki.cfg) switch to another installed authenticator.

Note that, by default, there is only one authenticator available (Standard XWiki Authenticator). So, if no authenticator extension was installed, it's not really possible to do anything for an attacker.

Also, in most cases, if you have installed and are using an SSO authenticator (like OIDC or LDAP for example), the worst an attacker can do is break authentication by switching back to the standard authenticator (that's because it's impossible to login to a user which does not have a stored password, and that's usually what SSO authenticator produce).

Patches

This has been patched in XWiki 15.10.9 and XWiki 16.3.0RC1.

Workarounds

You can very easily fix this vulnerability in your instance through right configuration:

access the page and children right administration of the page XWiki.Authentication (https://myhost/xwiki/bin/admin/XWiki/Authentication/WebPreferences?editor=spaceadmin&section=PageAndChildrenRights&space=XWiki.Authentication#|t=usersandgroupstable&p=1&l=10&uorg=groups&wiki=local&clsname=XWiki.XWikiGlobalRights)
make sure only admin user have the VIEW right

References

https://jira.xwiki.org/browse/XWIKI-22604 https://github.com/xwiki/xwiki-platform/commit/5efc31cea1501c9a5cb593566fea8b558ff32a2a

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-security-authentication-ui`	≥ 15.3-rc-1&&< 15.10.14	15.10.14
☕Maven	`org.xwiki.platform:xwiki-platform-security-authentication-ui`	≥ 16.0.0-rc-1&&< 16.4.6	16.4.6
☕Maven	`org.xwiki.platform:xwiki-platform-security-authentication-ui`	≥ 16.5.0-rc-1&&< 16.10.0-rc-1	16.10.0-rc-1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-security-authentication-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.xwiki.platform:xwiki-platform-security-authentication-ui to 15.10.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9c6-2f9p-82jj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-f9c6-2f9p-82jj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f9c6-2f9p-82jj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A user who can access pages located in the XWiki space (by default, anyone) can access the page `XWiki.Authentication.Administration` and (unless an authenticator is set in `xwiki.cfg`) switch to another installed authenticator. Note that, by default, there is only one authenticator available (`Standard XWiki Authenticator`). So, if no authenticator extension was installed, it's not really possible to do anything for an attacker. Also, in most cases, if you have installed and are using an SSO authenticator (like OIDC or LDAP for example), the worst an attacker can do is break aut

O3 Security · Impact-Aware SCA

Is GHSA-f9c6-2f9p-82jj in your dependencies?

O3 detects GHSA-f9c6-2f9p-82jj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-f9c6-2f9p-82jj

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-f9c6-2f9p-82jj in your dependencies?