Categories
CVE-2021-32620

Vulnerability in org.xwiki.commons:xwiki-commons-core (CVE-2021-32620)

Summary

Vulnerability in org.xwiki.commons:xwiki-commons-core (CVE-2021-32620). Successful exploitation can lead to full system takeover. Exploitable via validkey. Mitigation: upgrade to 12.10.2 or later.

Original description

The description as published by the source.

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. In versions prior to 11.10.13, 12.6.7, and 12.10.2, a user disabled on a wiki using email verification for registration canouldre-activate themself by using the activation link provided for his registration. The problem has been patched in the following versions of XWiki: 11.10.13, 12.6.7, 12.10.2, 13.0. It is 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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-32620 has been found in org.xwiki.commons:xwiki-commons-core.
Attackers can target a specific entry point like validkey over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.xwiki.commons:xwiki-commons-core to 12.10.2 or later.
If unsure, ask your IT team or search "org.xwiki.commons:xwiki-commons-core CVE-2021-32620" on the vendor's site.

CVE-2021-32620 (org.xwiki.commons:xwiki-commons-core) — CWE-285
Attack vector: remote (network-reachable) / no user interaction
Attack surface: validkey
Patched: 12.10.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-285) exists in org.xwiki.commons:xwiki-commons-core. Attackers reach the vulnerable code path via validkey.

📍 Affected scope

Check the vendor advisory for the affected versions of org.xwiki.commons:xwiki-commons-core. Attack surface: validkey.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 12.10.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.xwiki.commons:xwiki-commons-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.xwiki.commons:xwiki-commons-core to 12.10.2

    ステージング環境で 12.10.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.xwiki.commons:xwiki-commons-core
[{"type":"ECOSYSTEM","events":[{"introduced":"12.10.0"},{"fixed":"12.10.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details