# CVE-2025-32390: EspoCRM vulnerable to HTML Injection into phishing, which may lead to account takeover

> Authenticated users can inject HTML into Knowledge Base articles to deface pages and harvest credentials, leading to account takeover.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 12 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-qrwp-v8v3-hqp2

## What is CVE-2025-32390?

CVE-2025-32390 is a high-severity cross-site scripting vulnerability in espocrm, published on 12 May 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

EspoCRM is a free, open-source customer relationship management platform. Prior to version 9.0.8, HTML Injection in Knowledge Base (KB) articles leads to complete page defacement imitating the login page. Authenticated users with the read knowledge article privilege can browse to the KB article and if they submit their credentials, they get captured in plain text. The vulnerability is allowed by overly permissive HTML editing being allowed on the KB articles. Any authenticated user with the privilege to read KB articles is impacted. In an enterprise with multiple applications, the malicious KB article could be edited to match the login pages of other applications, which would make it useful for credential harvesting against other applications as well. Version 9.0.8 contains a patch for the issue.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Espocrm Espocrm.

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

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

## Is CVE-2025-32390 being exploited?

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

## Other vulnerabilities in espocrm

- [CVE-2014-7985](https://insights.sbomify.com/CVE-2014-7985/): Path traversal in n/a (critical 10.0)
- [CVE-2026-33656](https://insights.sbomify.com/CVE-2026-33656/): Path traversal in espocrm (critical 9.1)
- [CVE-2022-38843](https://insights.sbomify.com/CVE-2022-38843/): File upload in n/a (high 8.8)
- [CVE-2019-14351](https://insights.sbomify.com/CVE-2019-14351/): Information disclosure in n/a (high 8.8)
- [CVE-2020-37094](https://insights.sbomify.com/CVE-2020-37094/): EspoCRM 5.7.0 < 5.9.0 - Two-Factor Authentication Bypass via Auth Token Reuse Between Accounts with Identical Passwords (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32390 is a high-severity cross-site scripting vulnerability in espocrm, published on 12 May 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-32390 exists.

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

## Sources

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

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