EspoCRM allows arbitrary user creation via stored SVG injection and CSRF

published 2025-10-14 12 mo ago modified 2026-10-19 21 d ago also EUVD-2025-34207

cvss: 5.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits: 0; none known

EspoCRM is an open source customer relationship management application. In versions before 9.1.9, a vulnerability allows arbitrary user creation, including administrative accounts, through a combination of stored SVG injection and lack of CSRF protection. An attacker with Knowledge Base edit permissions can embed a malicious SVG element containing a link in the body field of an article. When an authenticated user clicks the malicious link, they are redirected to an attacker-controlled HTML page that executes a CSRF request against the api/v1/User endpoint. If the victim is prompted for and enters their credentials, an attacker-controlled account is created with privileges determined by the CSRF payload. This issue has been patched in version 9.1.9.

Patch / fix

fixed in 1

espocrm espocrm 9.1.9

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 12 mo ago (2025-10-14)

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/espocrm/espocrm/security/advisories/GHSA-c26c-wvhr-fr6r referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected products

espocrm espocrm

Classification

Weakness

CWE-352 Cross-Site Request Forgery
CWE-79 Improper Neutralization of Input During Web Page Generation

References

github.com /espocrm/espocrm/security/advisories/GHSA-c26c-wvhr-fr6r
exploit, mitigation, vendor-advisory

Sources

CVE List CVE-2025-59428
NVD CVE-2025-59428

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary