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.

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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.6%, placing it in the 48th 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

Not in CISA KEV

Any user with view access to the XWiki space can change the authenticatorGHSA-f9c6-2f9p-82jj

Fix: xwiki/xwiki-platform@5efc31c

GHSA-f9c6-2f9p-82jj is a CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-security-authentication-ui. A fix is available for org.xwiki.platform:xwiki-platform-security-authentication-ui — see the affected versions and patch details below.

Also known asCVE-2025-46557

Published

Apr 30, 2025

Updated

May 1, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-f9c6-2f9p-82jj.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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`org.xwiki.platform:xwiki-platform-security-authentication-ui:15.10.14`
☕Maven	`org.xwiki.platform:xwiki-platform-security-authentication-ui`	≥ 16.0.0-rc-1&&< 16.4.6	16.4.6`org.xwiki.platform:xwiki-platform-security-authentication-ui: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`org.xwiki.platform:xwiki-platform-security-authentication-ui:16.10.0-rc-1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 16.5.0 && ≤ 16.9.0

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works