CVE-2021-32620 is a high-severity (CVSS 8.8) CWE-285 vulnerability in org.xwiki.commons:xwiki-commons-core. O3 Security confirms whether CVE-2021-32620 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
XWiki users registered with email verification can self re-activate their disabled accounts
Real-World Exposure
org.xwiki.commons:xwiki-commons-core☕org.xwiki.commons:xwiki-commons-core☕org.xwiki.commons:xwiki-commons-coreReal-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
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. In versions prior to 11.10.13, 12.6.7, and 12.10.2, a user disabled on a wiki using email verification for registration canouldre-activate themself by using the activation link provided for his registration. The problem has been patched in the following versions of XWiki: 11.10.13, 12.6.7, 12.10.2, 13.0. It is possible to workaround the issue by resetting the validkey property of the disabled XWiki users. This can be done by editing the user profile with object editor.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.commons:xwiki-commons-core | ≥ 11.6&&< 11.10.13 | 11.10.13 |
| ☕Maven | org.xwiki.commons:xwiki-commons-core | ≥ 12.0&&< 12.6.7 | 12.6.7 |
| ☕Maven | org.xwiki.commons:xwiki-commons-core | ≥ 12.10.0&&< 12.10.2 | 12.10.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.commons:xwiki-commons-core. 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.commons:xwiki-commons-core to 11.10.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32620 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 CVE-2021-32620 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 CVE-2021-32620. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2021-32620 in your dependencies?
O3 detects CVE-2021-32620 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.