How severe is GHSA-5p82-2q3r-wj3m?

No CVSS score has been assigned to GHSA-5p82-2q3r-wj3m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5p82-2q3r-wj3m?

GHSA-5p82-2q3r-wj3m affects the following packages: org.thingsboard:application (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5p82-2q3r-wj3m?

Update org.thingsboard:application to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5p82-2q3r-wj3m is resolved across your whole dependency graph.

How do I detect GHSA-5p82-2q3r-wj3m in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.thingsboard:application, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5p82-2q3r-wj3m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5p82-2q3r-wj3m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5p82-2q3r-wj3m can be triaged on real exposure rather than presence alone.

Is GHSA-5p82-2q3r-wj3m actively exploited in the wild?

No public exploit code has been indexed for GHSA-5p82-2q3r-wj3m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5p82-2q3r-wj3m published, and has it been updated?

GHSA-5p82-2q3r-wj3m was published on November 27, 2025 and was last updated on December 2, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-5p82-2q3r-wj3m — application

Fix: thingsboard/thingsboard@b2ae6f9

GHSA-5p82-2q3r-wj3m is a security vulnerability in org.thingsboard:application. A fix is available for org.thingsboard:application — see the affected versions and patch details below.

ThingsBoard allows an authenticated user to upload malicious SVG images

Also known asCVE-2025-3261

Published

Nov 27, 2025

Updated

Dec 2, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕org.thingsboard:application

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an iframe element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the ImageController, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.thingsboard:application`	all versions	4.2.1`org.thingsboard:application:4.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.thingsboard:application, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.thingsboard:application to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5p82-2q3r-wj3m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5p82-2q3r-wj3m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5p82-2q3r-wj3m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image

O3 Security · Impact-Aware SCA

Is GHSA-5p82-2q3r-wj3m in your dependencies?

O3 Security finds GHSA-5p82-2q3r-wj3m across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works