How severe is CVE-2021-32620?

CVE-2021-32620 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-32620?

CVE-2021-32620 affects the following packages: org.xwiki.commons:xwiki-commons-core (Maven), org.xwiki.commons:xwiki-commons-core (Maven), org.xwiki.commons:xwiki-commons-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-32620?

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.

How do I detect CVE-2021-32620 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.commons:xwiki-commons-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-32620 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 CVE-2021-32620 actively exploited in the wild?

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

CVE-2021-32620 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-2021-32620?

CVE-2021-32620 is classified as CWE-285 (CWE-285), 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-2021-32620 published, and has it been updated?

CVE-2021-32620 was published on May 28, 2021 and was last updated on August 7, 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

HIGH severity

CVE-2021-32620 — xwiki-commons-core

HIGHFix: xwiki/xwiki-platform@f9a6774

CVE-2021-32620 is a high-severity (CVSS 8.8) CWE-285 vulnerability in org.xwiki.commons:xwiki-commons-core. A fix is available for org.xwiki.commons:xwiki-commons-core — see the affected versions and patch details below.

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

Also known asGHSA-76mp-659p-rw65

Published

May 28, 2021

Updated

Aug 7, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2021-32620 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕org.xwiki.commons:xwiki-commons-core☕org.xwiki.commons:xwiki-commons-core☕org.xwiki.commons:xwiki-commons-core

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 disabled on a wiki using email verification for registration can re-activate himself by using the activation link provided for his registration.

Patches

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

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.commons:xwiki-commons-core`	≥ 11.6&&< 11.10.13	11.10.13`org.xwiki.commons:xwiki-commons-core:11.10.13`
☕Maven	`org.xwiki.commons:xwiki-commons-core`	≥ 12.0&&< 12.6.7	12.6.7`org.xwiki.commons:xwiki-commons-core:12.6.7`
☕Maven	`org.xwiki.commons:xwiki-commons-core`	≥ 12.10.0&&< 12.10.2	12.10.2`org.xwiki.commons:xwiki-commons-core:12.10.2`

Affected Products

1 product · 4 configurations

Application

xwikixwiki

≥ 12.10.3 && < 13.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.commons:xwiki-commons-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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 disabled on a wiki using email verification for registration can re-activate himself by using the activation link provided for his registration. ### Patches The problem has been patched in the following versions of XWiki: 11.10.13, 12.6.7, 12.10.2, 13.0. ### 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 advis