# CVE-2025-34157: Coolify Stored Cross-Site Scripting (XSS) in Project Name Field

> Low-privilege users can inject JavaScript via project names, leading to admin session hijacking and full instance compromise in Coolify.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** No
- **Published:** 27 Aug 2025
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-6p37-qg9q-mprw

## What is CVE-2025-34157?

CVE-2025-34157 is a critical cross-site scripting vulnerability in coolLabs Technologies Coolify, published on 27 Aug 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

Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. An authenticated user with low privileges can create a project with a maliciously crafted name containing embedded JavaScript. When an administrator attempts to delete the project or its associated resource, the payload executes in the admin’s browser context. This results in full compromise of the Coolify instance, including theft of API tokens, session cookies, and access to WebSocket-based terminal sessions on managed servers.

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

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

It affects 1 product.


Products: Coollabs Coolify.

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

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

## Is CVE-2025-34157 being exploited?

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

Public exploit code:

- A stored XSS in the project delete flow allows execution of attacker-controlled JavaScript in an administrator’s browser when the admin attempts to delete a project created by a low-privileged user. This can lead to takeover of the Coolify instance (cookies, API tokens, WebSocket/terminal actions) (github_poc): https://github.com/Eyodav/CVE-2025-34157

## Other vulnerabilities in coolLabs Technologies Coolify

- [CVE-2025-59157](https://insights.sbomify.com/CVE-2025-59157/): Coolify has Git Repository RCE (critical 10.0)
- [CVE-2025-64420](https://insights.sbomify.com/CVE-2025-64420/): Coolify members can see private key of root user (critical 10.0)
- [CVE-2025-66209](https://insights.sbomify.com/CVE-2025-66209/): Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup (critical 10.0)
- [CVE-2025-22609](https://insights.sbomify.com/CVE-2025-22609/): Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE) (critical 10.0)
- [CVE-2025-22611](https://insights.sbomify.com/CVE-2025-22611/): Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE) (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34157 is a critical cross-site scripting vulnerability in coolLabs Technologies Coolify, published on 27 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-34157 in the wild and no public exploit code.

Affected product: coolLabs Technologies Coolify. 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-34157/ (Markdown: https://insights.sbomify.com/CVE-2025-34157/index.md)
```

## Sources

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

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