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

Advisory record · `GHSA-76mp-659p-rw65`

- **Identifiers:** `GHSA-76mp-659p-rw65` · `CVE-2021-32620`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 18 May 2021
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 May 2021, 18:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.xwiki.commons:xwiki-commons-core` (Maven): affected `>=11.6, <11.10.13 || >=12.0, <12.6.7 || >=12.10.0, <12.10.2`; fixed in `11.10.13`, `12.6.7`, `12.10.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected versions of xwiki-commons-core, a Maven package, are 11.6 up to but not including 11.10.13, 12.0 up to but not including 12.6.7, and 12.10.0 up to but not including 12.10.2. A user whose account was disabled on a wiki that uses email verification for registration can re-activate it themselves using the activation link from their registration. Upgrade to 11.10.13, 12.6.7, 12.10.2, or 13.0 or later. As a workaround, administrators can reset the validkey property of disabled users through the object editor on their user profile.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 67th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-76mp-659p-rw65)

## Sources

- [GitHub Advisory Database: GHSA-76mp-659p-rw65](https://github.com/advisories/GHSA-76mp-659p-rw65)
- [OSV: GHSA-76mp-659p-rw65](https://osv.dev/vulnerability/GHSA-76mp-659p-rw65)
- <https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-76mp-659p-rw65>
- <https://nvd.nist.gov/vuln/detail/CVE-2021-32620>
- <https://github.com/xwiki/xwiki-platform/commit/f9a677408ffb06f309be46ef9d8df1915d9099a4>
- <https://github.com/xwiki/xwiki-commons>
- <https://jira.xwiki.org/browse/XWIKI-17942>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-76mp-659p-rw65>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-76mp-659p-rw65/>. Everything for agents: <https://agentprime.io/llms.txt>.
