CVE
EspoCRM stored XSS in SVG attachment handling
Affects EspoCRM 10.0.0 before 10.0.8 and 9.3.10 and earlier, where low-privileged users can upload SVG images. Fixed in 10.0.8 and 9.3.11.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 10.0.8, 9.3.11
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. EspoCRM 10.0.0 before 10.0.8, or 9.3.10 and earlier A low-privileged user account that can upload SVG images
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.43% · 37th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
EspoCRM before 9.3.11 and 10.x before 10.0.8 contains a stored cross-site scripting vulnerability that allows low-privileged users to upload crafted SVG images that submit authenticated POST requests to arbitrary backend endpoints. Attackers can trick an administrator into opening the SVG in a separate browser tab and clicking it, performing administrator actions such as elevating the attacker's account to administrator.
Who should check
Teams running EspoCRM 10.0.0 to before 10.0.8 or 9.3.10 and earlier, where low-privileged users can upload files and administrators open them in a browser.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
EspoCRM 10.0.0 before 10.0.8, or 9.3.10 and earlier A low-privileged user account that can upload SVG imagesUpgrade to a fixed version: 10.0.8, 9.3.11.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126306 (EspoCRM before 10.0.8 Stored XSS via Malicious SVG Attachment), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126306 (entry last updated 2026-11-13):
Affected:
- espocrm espocrm: from 10.0.0, fixed in 10.0.8
- espocrm espocrm: fixed in 9.3.11
Fixed versions: 10.0.8, 9.3.11.
Conditions (all must be true for the bug to be hit):
- EspoCRM 10.0.0 before 10.0.8, or 9.3.10 and earlier (source: https://www.vulncheck.com/advisories/espocrm-before-10.0.8-stored-xss-via-malicious-svg-attachment)
- A low-privileged user account that can upload SVG images (source: https://www.vulncheck.com/advisories/espocrm-before-10.0.8-stored-xss-via-malicious-svg-attachment)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-126306 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126306 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/espocrm/espocrm/security/advisories/GHSA-4qv5-q4g7-hp5r
- https://www.vulncheck.com/advisories/espocrm-before-10.0.8-stored-xss-via-malicious-svg-attachment
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126306
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126306"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- espocrm espocrm
From 10.0.0 · fixed in 10.0.8
- espocrm espocrm
fixed in 9.3.11
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126306
Is CVE-2026-126306 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted SVG image uploaded to EspoCRM can carry script that is stored and runs when the image is viewed. The advisory says this can let an attacker perform actions with administrator privileges, including elevating their own account to administrator.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126306?
espocrm: from 10.0.0 before 10.0.8. espocrm: before 9.3.11.Source: cve.now feed data
Am I affected, and how do I check?
EspoCRM 10.0.0 before 10.0.8, and 9.3.10 and earlier. The affected setup requires a low-privileged user account that can upload SVG images. A reader can check the installed EspoCRM version number and whether SVG uploads are allowed for non-admin accounts.Source: vulncheck.com, github.com
How do I fix CVE-2026-126306?
Upgrade to EspoCRM 10.0.8 or 9.3.11, the fixed versions listed for this vulnerability. The facts name no vendor patch ids.Source: vulncheck.com, github.com