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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a small standalone Python proof-of-concept exploit for CVE-2025-34282, an authenticated SSRF issue in ThingsBoard IoT Platform before 4.2.1. The repo contains three files: a README describing the vulnerability and attack chain, a malicious SVG sample (ssrf_localhost_5555.svg), and the main exploit script (thingsboard_4.2.0_ssrf_CVE-2025-34282_exploit.py). The exploit script uses the requests library and is the sole code file. Its workflow is straightforward: first, upload a user-supplied image file to the ThingsBoard image API (/api/image) using a bearer token in the X-Authorization header; second, parse the JSON response to extract the returned publicLink; third, create a widget through /api/widgetType whose HTML template embeds that publicLink in an <object> tag. The intended effect is that ThingsBoard processes the uploaded SVG server-side and fetches the remote resource referenced in the SVG's xlink:href, thereby causing SSRF. The sample SVG targets http://127.0.0.1:5555 to demonstrate access to localhost-only services from the server. Capabilities: authenticated upload of a crafted SVG, automated extraction of the uploaded file's public link, automated widget creation to trigger rendering, and SSRF against attacker-chosen internal URLs embedded in the SVG. The exploit does not provide code execution or a shell payload; it is focused on inducing outbound HTTP requests from the vulnerable server. The script is operational but basic: target URLs are hardcoded to localhost:8080, and the attacker must already have a valid Tenant Admin token. The repository is not part of a larger exploit framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.