Categories
CVE-2021-32621

Code Injection in org.xwiki.commons:xwiki-commons-core (CVE-2021-32621)

Summary

Code injection in org.xwiki.commons:xwiki-commons-core (CVE-2021-32621). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 12.10.3 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 12.6.7 and 12.10.3, a user without Script or Programming right is able to execute script requiring privileges by editing gadget titles in the dashboard. The issue has been patched in XWiki 12.6.7, 12.10.3 and 13.0RC1.

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-32621 has been found in org.xwiki.commons:xwiki-commons-core.
Successful exploitation can lead to full system takeover.
What to do: upgrade org.xwiki.commons:xwiki-commons-core to 12.10.3 or later.
If unsure, ask your IT team or search "org.xwiki.commons:xwiki-commons-core CVE-2021-32621" on the vendor's site.

CVE-2021-32621 (org.xwiki.commons:xwiki-commons-core) — CWE-94
Attack vector: remote (network-reachable) / no user interaction
Patched: 12.10.3 — 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

Arbitrary code execution (CWE-94) exists in org.xwiki.commons:xwiki-commons-core.

📍 Affected scope

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

🔥 Severity

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

🔧 How to fix

Update to 12.10.3.

🛡️ 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.3

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

  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.3"}]}]

References

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