How severe is CVE-2025-29924?

No CVSS score has been assigned to CVE-2025-29924 yet. Review the advisory details and affected package list to assess your exposure.

How do I fix CVE-2025-29924?

Update org.xwiki.platform:xwiki-platform-security-authorization-api to 15.10.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-29924 is resolved across your whole dependency graph.

How do I detect CVE-2025-29924 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-authorization-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-29924 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2025-29924 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-29924 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 CVE-2025-29924?

CVE-2025-29924 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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 CVE-2025-29924?

CVE-2025-29924 is classified as Improper Privilege Management (CWE-269), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-29924 published, and has it been updated?

CVE-2025-29924 was published on March 19, 2025 and was last updated on October 28, 2026. 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

CVE-2025-29924 — xwiki-platform-security-a…

Fix: xwiki/xwiki-platform@5f98bde

CVE-2025-29924 is a Improper Privilege Management vulnerability in org.xwiki.platform:xwiki-platform-security-authorization-api. A fix is available for org.xwiki.platform:xwiki-platform-security-authorization-api — see the affected versions and patch details below.

XWiki uses the wrong wiki reference in AuthorizationManager

Also known asGHSA-gq32-758c-3wm3

Published

Mar 19, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-29924.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% 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-authorization-api☕org.xwiki.platform:xwiki-platform-security-authorization-api☕org.xwiki.platform:xwiki-platform-security-authorization-api

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

It's possible for an user to get access to private information through the REST API - but could also be through another API - when a sub wiki is using "Prevent unregistered users to view pages". The vulnerability only affects subwikis, and it only concerns specific right options such as "Prevent unregistered users to view pages". or "Prevent unregistered users to edit pages".

It's possible to detect the vulnerability by enabling "Prevent unregistered users to view pages" and then trying to access a page through the REST API without using any credentials.

Patches

The vulnerability has been patched in XWiki 15.10.14, 16.4.6 and 16.10.0RC1.

Workarounds

There's no workaround.

References

JIRA ticket: https://jira.xwiki.org/browse/XWIKI-22640
Commit of the fix: https://github.com/xwiki/xwiki-platform/commit/5f98bde87288326cf5787604e2bb87836875ed0e

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

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 16.5.0 && ≤ 16.10.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-authorization-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-security-authorization-api to 15.10.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-29924 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### Impact It's possible for an user to get access to private information through the REST API - but could also be through another API - when a sub wiki is using "Prevent unregistered users to view pages". The vulnerability only affects subwikis, and it only concerns specific right options such as "Prevent unregistered users to view pages". or "Prevent unregistered users to edit pages". It's possible to detect the vulnerability by enabling "Prevent unregistered users to view pages" and then trying to access a page through the REST API without using any credentials. ### Patches The vulnerab

O3 Security · Impact-Aware SCA

Is CVE-2025-29924 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works