# CVE-2025-0607: HTML Injection in Logo Software's Logo Cloud

> Attackers can inject malicious HTML into Logo Cloud to facilitate phishing attacks, potentially compromising user accounts.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **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:** 6 Oct 2025
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-x72w-3h7j-3f2r

## What is CVE-2025-0607?

CVE-2025-0607 is a medium-severity cross-site scripting vulnerability in Logo Cloud, published on 6 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Improper Encoding or Escaping of Output vulnerability in Logo Software Inc. Logo Cloud allows Phishing.

This issue affects Logo Cloud: before 2.57.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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


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

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

## Is CVE-2025-0607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0607 is a medium-severity cross-site scripting vulnerability in Logo Cloud, published on 6 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-0607 in the wild and no public exploit code.

Affected product: Logo Cloud. 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-0607/ (Markdown: https://insights.sbomify.com/CVE-2025-0607/index.md)
```

## Sources

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

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