Skip to content

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

High severity GitHub Reviewed Published May 18, 2021 in xwiki/xwiki-platform • Updated Jan 27, 2023

Package

maven org.xwiki.commons:xwiki-commons-core (Maven)

Affected versions

>= 12.0, < 12.6.7
>= 12.10.0, < 12.10.2
>= 11.6, < 11.10.13

Patched versions

12.6.7
12.10.2
11.10.13

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:

References

@surli surli published to xwiki/xwiki-platform May 18, 2021
Reviewed May 18, 2021
Published to the GitHub Advisory Database May 18, 2021
Published by the National Vulnerability Database May 28, 2021
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.222%
(61st percentile)

Weaknesses

CVE ID

CVE-2021-32620

GHSA ID

GHSA-76mp-659p-rw65

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.