CVE-2021-32620

XWiki users registered with email verification can self re-activate their disabled accounts

Workarounds

It's 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.

References

https://jira.xwiki.org/browse/XWIKI-17942

For more information

If you have any questions or comments about this advisory:

• Open an issue in Jira
• Email us at Security mailing-list

A user disabled on a wiki using email verification for registration can re-activate himself by using the activation link provided for his registration.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2021-32620 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.6.7, 12.10.2, 11.10.13); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been patched in the following versions of XWiki: 11.10.13, 12.6.7, 12.10.2, 13.0.

1. What is CVE-2021-32620? CVE-2021-32620 is a high-severity incorrect authorization vulnerability in org.xwiki.commons:xwiki-commons-core (maven), affecting versions >= 12.0, < 12.6.7. It is fixed in 12.6.7, 12.10.2, 11.10.13. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2021-32620? CVE-2021-32620 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.xwiki.commons:xwiki-commons-core are affected by CVE-2021-32620? org.xwiki.commons:xwiki-commons-core (maven) versions >= 12.0, < 12.6.7 is affected.
4. Is there a fix for CVE-2021-32620? Yes. CVE-2021-32620 is fixed in 12.6.7, 12.10.2, 11.10.13. Upgrade to this version or later.
5. Is CVE-2021-32620 exploitable, and should I be worried? Whether CVE-2021-32620 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2021-32620 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2021-32620?
   • Upgrade org.xwiki.commons:xwiki-commons-core to 12.6.7 or later
   • Upgrade org.xwiki.commons:xwiki-commons-core to 12.10.2 or later
   • Upgrade org.xwiki.commons:xwiki-commons-core to 11.10.13 or later

Other vulnerabilities in org.xwiki.commons:xwiki-commons-core