# CVE-2025-51991: Code injection in n/a

> Authenticated administrators can inject Velocity code in XWiki preferences, potentially leading to remote code execution or data leakage.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** No
- **Published:** 20 Aug 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-94x5-j7vw-fqv4

## What is CVE-2025-51991?

CVE-2025-51991 is a high-severity code injection vulnerability in Xwiki Xwiki, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

XWiki through version 17.3.0 is vulnerable to Server-Side Template Injection (SSTI) in the Administration interface, specifically within the HTTP Meta Info field of the Global Preferences Presentation section. An authenticated administrator can inject crafted Apache Velocity template code, which is rendered on the server side without proper validation or sandboxing. This enables the execution of arbitrary template logic, which may expose internal server information or, in specific configurations, lead to further exploitation such as remote code execution or sensitive data leakage. The vulnerability resides in improper handling of dynamic template rendering within user-supplied configuration fields.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-51991?

It affects 1 product.


Products: Xwiki Xwiki.

## How do I fix CVE-2025-51991?

No fix has been published for CVE-2025-51991 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-51991 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51991 exists.

Public exploit code:

- XWiki <= 17.3.0 - Server-Side Template Injection (SSTI) (nuclei): http/cves/2025/CVE-2025-51991.yaml

## 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-2025-51991 and fix it if it is affected.

What it is: CVE-2025-51991 is a high-severity code injection vulnerability in Xwiki Xwiki, published on 20 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51991 exists.

Affected product: Xwiki Xwiki. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-51991/ (Markdown: https://insights.sbomify.com/CVE-2025-51991/index.md)
```

## Sources

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

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