Security readout for executives and security teams
Plain-English summary
Vulnerable XWiki instances can reveal whether an email address belongs to a wiki account and which username is tied to it. The issue is in the Forgot username page and can be abused without authentication. This is primarily a confidentiality risk that can support account discovery and targeted follow-on attacks.
Executive priority
Treat this as a high-priority privacy and reconnaissance issue for any exposed XWiki service. It does not indicate system takeover, but it can reveal user identities and support phishing, password attacks, or account targeting. Prioritize upgrade or vendor workaround on public and sensitive wikis.
Technical view
CVE-2021-32732 is a CSRF weakness in xwiki-platform's Forgot username flow. Because the page lacked CSRF protection, forged requests could enumerate account existence and usernames associated with email addresses. XWiki fixed this in 12.10.5 and 13.2RC1, including a CSRF fix and a redesigned email-based recovery flow.
Likely exposure
Exposure is likely for XWiki deployments running versions before 12.10.5, or 13.0 through before 13.2RC1, where the Forgot username functionality is reachable. Internet-facing knowledge bases, partner portals, and internal wikis exposed through VPN or SSO should be checked.
Exploitation context
The sources describe an unauthenticated, network-reachable confidentiality issue with low attack complexity. CISA KEV status is false in the supplied bundle, and no cited source states active exploitation. The practical risk is account and username enumeration, not direct code execution or data modification.
Researcher notes
The provided evidence identifies CWE-352 and CVSS 3.1 7.5 with confidentiality impact only. Scope affected versions precisely; do not assume other XWiki products are affected from this bundle alone. The commits and Jira references support the CSRF fix and revised Forgot username behavior.
Mitigation direction
- Upgrade XWiki to 12.10.5, 13.2RC1, or a later supported release.
- For pre-13.x deployments, apply the vendor ForgotUsername page workaround if immediate upgrade is blocked.
- For 13.x deployments, follow vendor guidance; manual template editing is discouraged compared with upgrading.
- Review public exposure of the Forgot username page until remediation is complete.
- Check vendor advisories for any version-specific maintenance guidance.
Validation and detection
- Inventory all XWiki deployments and record exact platform versions.
- Confirm whether any deployment matches <12.10.5 or >=13.0,<13.2RC1.
- Verify the Forgot username page is patched or replaced with the vendor-supported flow.
- Review change history for local customizations to ForgotUsername or forgotusername.vm.
- Confirm remediation through normal recovery-flow testing without bulk enumeration.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2021-32732 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-vh5c-jqfg-mhrhCVE reference · x_refsource_CONFIRM
- https://github.com/xwiki/xwiki-platform/commit/69548c0320cbd772540cf4668743e69f879812cfCVE reference · x_refsource_MISC
- https://github.com/xwiki/xwiki-platform/commit/f0440dfcbba705e03f7565cd88893dde57ca3fa8CVE reference · x_refsource_MISC
- https://jira.xwiki.org/browse/XWIKI-18384CVE reference · x_refsource_MISC
- https://jira.xwiki.org/browse/XWIKI-18408CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.