# CVE-2025-51990: Cross-site scripting in n/a

> Authenticated administrators can inject persistent JavaScript into global preferences, leading to session hijacking and credential theft for all site visitors.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-6jx2-qgxg-f4q9

## What is CVE-2025-51990?

CVE-2025-51990 is a medium-severity cross-site scripting vulnerability in Xwiki Xwiki, published on 20 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

XWiki through version 17.3.0 is affected by multiple stored Cross-Site Scripting (XSS) vulnerabilities in the Administration interface, specifically under the Presentation section of the Global Preferences panel. An authenticated administrator can inject arbitrary JavaScript payloads into the HTTP Meta Info, Footer Copyright, and Footer Version fields. These inputs are stored and subsequently rendered without proper output encoding or sanitization on public-facing pages. As a result, the injected scripts are persistently executed in the browser context of any visitor to the affected instances including both authenticated and unauthenticated users. No user interaction is required beyond visiting a page that includes the malicious content. Successful exploitation can lead to session hijacking, credential theft, unauthorized actions via session riding, or further compromise of the application through client-side attacks. The vulnerability introduces significant risk in any deployment, especially in shared or internet-facing environments where administrator credentials may be compromised.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Xwiki Xwiki.

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

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

## Is CVE-2025-51990 being exploited?

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

Public exploit code:

- XWiki – Stored Cross-Site Scripting (XSS) (nuclei): http/cves/2025/CVE-2025-51990.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-51990 and fix it if it is affected.

What it is: CVE-2025-51990 is a medium-severity cross-site scripting vulnerability in Xwiki Xwiki, published on 20 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51990 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-51990/ (Markdown: https://insights.sbomify.com/CVE-2025-51990/index.md)
```

## Sources

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

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