Security readout for executives and security teams
Plain-English summary
Coolify had a stored XSS flaw where a low-privileged authenticated user could plant script in a project name. When an administrator later deleted that project or resource, the script could run with admin browser privileges, risking takeover of the Coolify instance and connected server access.
Executive priority
Treat this as urgent where Coolify manages production infrastructure. A successful attack could convert a low-privilege account into administrative control over deployment infrastructure and managed servers.
Technical view
The bundle describes stored XSS in Coolify project creation before v4.0.0-beta.420.6, triggered during administrator deletion flows. Impact includes token or cookie theft and access to WebSocket terminal sessions. CVSS 4.0 is 9.4 with low attack complexity, low privileges required, and user interaction by an admin.
Likely exposure
Exposure is likely limited to organizations running Coolify versions before the fixed beta release and allowing non-admin authenticated users to create projects. Internet-facing or shared-team Coolify instances have higher practical risk.
Exploitation context
The CVE is not listed as KEV in the bundle, so active exploitation is not established. A public technical/exploit reference is cited, which raises urgency, but the provided evidence does not prove real-world exploitation.
Researcher notes
Key evidence comes from the CVE description, CVSS vector, vendor release reference, and public technical repository. The affected version data in the bundle is sparse, so version confirmation should rely on vendor release notes and local inventory.
Mitigation direction
- Upgrade Coolify to the vendor-recommended fixed release, referenced as v4.0.0-beta.420.7.
- Restrict project creation to trusted users until patched.
- Review Coolify sessions, API tokens, and administrator activity after remediation.
- Rotate exposed tokens or credentials if suspicious project names or admin actions are found.
- Check vendor guidance for any additional cleanup steps.
Validation and detection
- Inventory Coolify instances and record exact running versions.
- Confirm whether any instance is older than the fixed vendor release.
- Review project names for unexpected script-like content.
- Check audit logs for low-privilege project creation followed by administrator deletion actions.
- Verify patched instances no longer render project names as executable script.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-34157 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.420.7CVE reference, VulnCheck · vendor-advisory, patch
- https://coolify.io/CVE reference, VulnCheck · product
- https://github.com/Eyodav/CVE-2025-34157CVE reference, VulnCheck · technical-description, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.