CVE-2025-34282 json
ThingsBoard < v4.2.1 SVG Image SSRF
published 2025-10-17 12 mo ago modified 2026-11-08 19 h ago also EUVD-2025-34906
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 1
- Exploit-DB
Summary
ThingsBoard versions < 4.2.1 contain a server-side request forgery (SSRF) vulnerability in the dashboard's Image Upload Gallery feature. An attacker can upload a malicious SVG file that references a remote URL. If the server processes the SVG file in a way that parses external references, it may initiate unintended outbound requests. This can be used to access internal services or resources.
Patch / fix
- ThingsBoard, Inc. ThingsBoard 4.2.1
Timeline
- Published
- First public exploit (EDB-52551)
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
1.82% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-52551 ThingsBoard IoT Platform 4.2.0 - Server-Side Request Forgery (SSRF) webapps, 2026-05-07
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected products
- ThingsBoard, Inc. ThingsBoard
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/thingsboard/thingsboard/releases/tag/v4.2.1
release-notes, patch
-
github.com
/thingsboard/thingsboard/pull/13927
issue-tracking, patch
-
vulncheck.com
/advisories/thingsboard-svg-image-ssrf
third-party-advisory
Sources
- CVE List CVE-2025-34282
- NVD CVE-2025-34282
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.