# CVE-2025-7053: Cockpit save cross site scripting

> Remote attackers can inject malicious scripts via user name or email fields in Cockpit, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-j4rj-fgcq-wmqp

## What is CVE-2025-7053?

CVE-2025-7053 is a medium-severity cross-site scripting vulnerability in Cockpit, published on 4 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Cockpit up to 2.11.3. It has been rated as problematic. This issue affects some unknown processing of the file /system/users/save. The manipulation of the argument name/email leads to cross site scripting. The attack may be initiated remotely. Upgrading to version 2.11.4 is able to address this issue. The patch is named bdcd5e3bc651c0839c7eea807f3eb6af856dbc76. It is recommended to upgrade the affected component. The vendor was contacted early about this disclosure and acted very professional. A patch and new release was made available very quickly.

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-7053?

2 open source packages ship an affected version, including cockpit-hq/cockpit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cockpit-hq/cockpit` | Packagist | All versions | 2.11.4 |
| `cockpit-hq/cockpit` | Packagist | All versions | 2.11.4 |

Products: Agentejo Cockpit.

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

Upgrade cockpit-hq/cockpit to 2.11.4 or later.

## Is CVE-2025-7053 being exploited?

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

## Other vulnerabilities in Cockpit

- [CVE-2023-4195](https://insights.sbomify.com/CVE-2023-4195/): PHP Remote File Inclusion in cockpit-hq/cockpit (critical 9.9)
- [CVE-2024-4825](https://insights.sbomify.com/CVE-2024-4825/): Unrestricted Upload of File with Dangerous Type vulnerability on Cockpit CMS from Agentejo (critical 9.8)
- [CVE-2022-2818](https://insights.sbomify.com/CVE-2022-2818/): Improper Removal of Sensitive Information Before Storage or Transfer in cockpit-hq/cockpit (critical 9.8)
- [CVE-2020-35131](https://insights.sbomify.com/CVE-2020-35131/): Code injection in n/a (critical 9.8)
- [CVE-2020-35846](https://insights.sbomify.com/CVE-2020-35846/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7053 and fix it if it is affected.

What it is: CVE-2025-7053 is a medium-severity cross-site scripting vulnerability in Cockpit, published on 4 Jul 2025. Any signed-in user can exploit it over the network, 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-7053 exists.

Affected packages and fixed versions:
- cockpit-hq/cockpit (Packagist): affected all versions; fixed in 2.11.4
- cockpit-hq/cockpit (Packagist): affected all versions; fixed in 2.11.4

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

## Sources

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

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