# CVE-2020-15252: RCE in XWiki

> Users with script rights can execute arbitrary code by accessing the Servlet context to instantiate Java objects.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5hv6-mh8q-q9v8

## What is CVE-2020-15252?

CVE-2020-15252 is a high-severity code injection vulnerability in Xwiki Xwiki, published on 16 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2020-15252?

4 open source packages ship an affected version, including org.xwiki.platform:xwiki-platform-oldcore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.xwiki.platform:xwiki-platform-oldcore` | Maven | All versions | 11.10.6 |
| `org.xwiki.platform:xwiki-platform-oldcore` | Maven | All versions | 11.10.6 |
| `org.xwiki.platform:xwiki-platform-oldcore` | Maven | From 12.0 | 12.5 |
| `org.xwiki.platform:xwiki-platform-oldcore` | Maven | From 12.0 | 12.5 |

Products: Xwiki Xwiki.

## How do I fix CVE-2020-15252?

Upgrade org.xwiki.platform:xwiki-platform-oldcore to a fixed version for your release line: 11.10.6 or 12.5.

## Is CVE-2020-15252 being exploited?

There is no known exploitation of CVE-2020-15252 in the wild and no public exploit code.

## Other vulnerabilities in Xwiki Xwiki

- [CVE-2025-24893](https://insights.sbomify.com/CVE-2025-24893/): XWiki Platform Eval Injection (critical 9.8, exploited in the wild)
- [CVE-2025-53836](https://insights.sbomify.com/CVE-2025-53836/): XWiki Rendering is vulnerable to RCE attacks when processing nested macros (critical 10.0)
- [CVE-2024-55662](https://insights.sbomify.com/CVE-2024-55662/): XWiki allows remote code execution through the extension sheet (critical 10.0)
- [CVE-2024-55877](https://insights.sbomify.com/CVE-2024-55877/): XWiki allows remote code execution from account through macro descriptions and XWiki.XWikiSyntaxMacrosList (critical 10.0)
- [CVE-2024-37901](https://insights.sbomify.com/CVE-2024-37901/): XWiki Platform vulnerable to remote code execution from account via SearchSuggestConfigSheet (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15252 and fix it if it is affected.

What it is: CVE-2020-15252 is a high-severity code injection vulnerability in Xwiki Xwiki, published on 16 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15252 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.xwiki.platform:xwiki-platform-oldcore (Maven): affected all versions; fixed in 11.10.6
- org.xwiki.platform:xwiki-platform-oldcore (Maven): affected all versions; fixed in 11.10.6
- org.xwiki.platform:xwiki-platform-oldcore (Maven): affected from 12.0; fixed in 12.5
- org.xwiki.platform:xwiki-platform-oldcore (Maven): affected from 12.0; fixed in 12.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-15252/ (Markdown: https://insights.sbomify.com/CVE-2020-15252/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-15252
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-15252
- OSV: https://osv.dev/vulnerability/CVE-2020-15252

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-15252/
Summaries are generated and may contain mistakes; the official description above is the record.