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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2021-32620: 1.13% estimated exploitation activity in the next 30 days; percentile 66.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

18 May 2021, 18:36 UTC

Last modified by the source

22 Jan 2025, 17:40 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-76mp-659p-rw65

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-32620

Advisory: XWiki users registered with email verification can self re-activate their disabled accounts
IDs: CVE-2021-32620, GHSA-76mp-659p-rw65
Record: https://patchnext.com/advisories/cve-2021-32620 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.xwiki.commons:xwiki-commons-core 12.10.2, 12.6.7, 11.10.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.xwiki.commons:xwiki-commons-core: affected >= 12.0, < 12.6.7; >= 12.10.0, < 12.10.2; >= 11.6, < 11.10.13; fixed in 12.6.7, 11.10.13, 12.10.2

## Suggested inspection (read-only)
- Maven org.xwiki.commons:xwiki-commons-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.xwiki.commons:xwiki-commons-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-76mp-659p-rw65 (GitHub-reviewed advisory GHSA-76mp-659p-rw65 lists affected ranges: Maven org.xwiki.commons:xwiki-commons-core >=12.0 =12.10.0 =11.6 <11.10.13)

Commands are suggestions: review each one before running it.