LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32729: A user without PR can reset user authentication failures information

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. A vulnerability exists in versions prior to 12.6.88, 12.10.4, and 13.0. The script service method used to reset the authentication failures record can be executed by any user with Script rights and does not require Programming rights. An attacher with script rights who is able to reset the authentication failure record might perform a brute force attack, since they would be able to virtually deactivate the mechanism introduced to mitigate those attacks. The problem has been patched in version 12.6.8, 12.10.4 and 13.0. There are no workarounds aside from upgrading.

LowCVSS 2Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This flaw lets a highly privileged XWiki user reset authentication-failure records without Programming rights. That can weaken the lockout-style protection meant to slow brute-force attempts. It is not a direct data theft issue, but it can reduce account protection in affected XWiki deployments.

Executive priority

Treat as a low-severity hardening fix. Schedule upgrade in normal maintenance, but move faster for public or shared XWiki environments where Script rights are broadly delegated.

Technical view

The vulnerable XWiki Platform script service method for resetting authentication failures required Script rights but not Programming rights. A user with Script rights could clear failure records and effectively bypass the brute-force mitigation. Impact is limited integrity degradation of authentication defense, with CVSS 3.1 score 2.0.

Likely exposure

Exposure is limited to XWiki Platform versions greater than 11.6RC1 and below 12.6.8, or 12.10.0 through before 12.10.4, especially where non-administrators have Script rights.

Exploitation context

The bundle does not show active exploitation, and KEV is false. Practical abuse requires authenticated access with Script rights and is constrained by high privileges and user interaction noted in CVSS.

Researcher notes

The source text contains one apparent version typo, saying 12.6.88 once, while affected ranges and patch statement identify 12.6.8. Use the affected ranges and vendor advisory as the authoritative basis.

Mitigation direction

  • Upgrade affected XWiki Platform instances to 12.6.8, 12.10.4, 13.0, or later supported releases.
  • Prioritize systems where Script rights are granted beyond trusted administrators.
  • Review vendor advisory and Jira issue for deployment-specific guidance.
  • There are no named workarounds aside from upgrading in the source bundle.

Validation and detection

  • Inventory XWiki Platform versions and compare against the affected ranges.
  • Confirm upgraded instances run 12.6.8, 12.10.4, 13.0, or later.
  • Review which users or groups hold Script rights.
  • Check whether non-administrative users can influence pages using script services.
  • Record findings and remediation status in vulnerability management tracking.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-693: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32729 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N0.51.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2Low
CVSS 3.1 vector shape for CVE-2021-32729Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
xwikixwiki-platform> 11.6RC1, < 12.6.8, >= 12.10.0, < 12.10.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.