Categories
CVE-2020-15252

Vulnerability in org.xwiki.platform:xwiki-platform-oldcore (CVE-2020-15252)

Summary

Vulnerability in org.xwiki.platform:xwiki-platform-oldcore (CVE-2020-15252). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 12.5 or later.

Original description

The description as published by the source.

In XWiki before version 12.5 and 11.10.6, any user with SCRIPT right (EDIT right before XWiki 7.4) can gain access to the application server Servlet context which contains tools allowing to instantiate arbitrary Java objects and invoke methods that may lead to arbitrary code execution. This is patched in XWiki 12.5 and XWiki 11.10.6.

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

CVE-2020-15252 (org.xwiki.platform:xwiki-platform-oldcore) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Patched: 12.5 — 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-74) exists in org.xwiki.platform:xwiki-platform-oldcore.

📍 Affected scope

Check the vendor advisory for the affected versions of org.xwiki.platform:xwiki-platform-oldcore.

🔥 Severity

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

🔧 How to fix

Update to 12.5.

🛡️ 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.platform:xwiki-platform-oldcore を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.xwiki.platform:xwiki-platform-oldcore to 12.5

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

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

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

Affected packages

Maven org.xwiki.platform:xwiki-platform-oldcore
[{"type":"ECOSYSTEM","events":[{"introduced":"12.0"},{"fixed":"12.5"}]}]

References

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