# CVE-2026-53575: EspoCRM: Persistent XSS via CSP nonce injection in applicationName setting by admin user

> An authenticated administrator can inject persistent JavaScript via the applicationName setting, allowing session hijacking and data leakage for other users.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-f34h-xxmv-j9xp

## What is CVE-2026-53575?

CVE-2026-53575 is a low-severity cross-site scripting vulnerability in espocrm, published on 15 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

EspoCRM is an open source customer relationship management application. Prior to 9.3.9, an authenticated administrator can place crafted content in the applicationName setting through CSP nonce injection. The persistent injection is inserted into the main application page without escaping, allowing attacker-controlled JavaScript to run in users' sessions and leak page data, including unsaved user input. This issue is fixed in version 9.3.9.

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

## Which versions are affected by CVE-2026-53575?


## How do I fix CVE-2026-53575?

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

## Is CVE-2026-53575 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53575 and fix it if it is affected.

What it is: CVE-2026-53575 is a low-severity cross-site scripting vulnerability in espocrm, published on 15 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53575 in the wild and no public exploit code.

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

## Sources

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

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