CVE-2025-62430 ClipBucket v5 stored XSS via video/photo fields

Medium 5.4 Published Updated

Attackers can inject malicious scripts into video or photo metadata fields, allowing execution in victim browsers to steal data or perform actions.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2025-62430?

CVE-2025-62430 is a medium-severity cross-site scripting vulnerability in MacWarrior clipbucket-v5, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

ClipBucket v5 is an open source video sharing platform. ClipBucket v5 through build 5.5.2 #145 allows stored cross-site scripting (XSS) in multiple video and photo metadata fields. For videos the Tags field and the Genre, Actors, Producer, Executive Producer, and Director fields in Movieinfos accept user supplied values without adequate sanitization. For photos the Photo Title and Photo Tags fields accept user supplied values without adequate sanitization. A regular user who can edit a video or photo can inject script (for example by supplying a value such as a closing delimiter followed by a script element). The injected script executes when any user, including an unauthenticated visitor or an administrator, views the affected video or photo page. Although cookies are set with the HttpOnly attribute and cannot be read directly, the injected script can issue fetch requests to endpoints such as admin_area pages and exfiltrate their contents or trigger unintended actions. Version 5.5.2 build #146 and later contain a fix. Update to build 5.5.2 #146 or later. No known workarounds exist.

Weakness: CWE-79

Which versions are affected by CVE-2025-62430?

It affects 1 product.

Products include Oxygenz Clipbucket.

How do I fix CVE-2025-62430?

No fix has been published for CVE-2025-62430 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2025-62430 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62430 exists.

Sources

Also known as GHSA-qrqq-hpf3-9mc9.

Is CVE-2025-62430 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free