Loading...
Skip to main content

CVE-2025-46557 — Vulnerability in...

HIGH

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

Published April 30, 2025Updated May 1, 2025Source: osv

Summary

### 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](https://jira.xwiki.org/) * Email us at [Security Mailing List](mailto:security@xwiki.org)

Advisory Timeline

  • First published April 30, 2025 (530 days ago).
  • Last revised May 1, 2025 — 1 day after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.xwiki.platform:xwiki-platform-security-authentication-ui to 15.10.14 or later
<!-- Update pom.xml dependency version to 15.10.14 for org.xwiki.platform:xwiki-platform-security-authentication-ui -->
Maven
Update org.xwiki.platform:xwiki-platform-security-authentication-ui to 16.4.6 or later
<!-- Update pom.xml dependency version to 16.4.6 for org.xwiki.platform:xwiki-platform-security-authentication-ui -->
Maven
Update org.xwiki.platform:xwiki-platform-security-authentication-ui to 16.10.0-rc-1 or later
<!-- Update pom.xml dependency version to 16.10.0-rc-1 for org.xwiki.platform:xwiki-platform-security-authentication-ui -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 1 ecosystem: maven (1).

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-862
    Missing AuthorizationMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.9 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N

Frequently Asked Questions

What is CVE-2025-46557?
Any user with view access to the XWiki space can change the authenticator This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.9/10).
How do I check if my project is affected by CVE-2025-46557?
CVE-2025-46557 affects org.xwiki.platform:xwiki-platform-security-authentication-ui. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-46557 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.9

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-f9c6-2f9p-82jj

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies