Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-54421: Cross-Site Request Forgery (CSRF) in Sanjay_Negi Floating Video Player

0
Unknown
VulnerabilityCVE-2024-54421cvecve-2024-54421
Published: Mon Dec 16 2024 (12/16/2024, 14:13:51 UTC)
Source: CVE Database V5
Vendor/Project: Sanjay_Negi
Product: Floating Video Player

Description

Cross-Site Request Forgery (CSRF) vulnerability in Sanjay_Negi Floating Video Player floating-player allows Stored XSS.This issue affects Floating Video Player: from n/a through <= 1.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 04:58:39 UTC

Technical Analysis

CVE-2024-54421 identifies a security vulnerability in the Floating Video Player developed by Sanjay_Negi, specifically versions up to and including 1.0. The vulnerability is a Cross-Site Request Forgery (CSRF) issue that facilitates Stored Cross-Site Scripting (XSS) attacks. CSRF vulnerabilities allow attackers to trick authenticated users into submitting unwanted requests to a web application, which in this case results in the injection and storage of malicious scripts within the video player’s context. Stored XSS is particularly dangerous because the malicious payload is saved on the server and served to other users, potentially compromising multiple users’ browsers. The vulnerability arises due to insufficient validation and lack of CSRF protections in the Floating Video Player plugin. While no exploits have been reported in the wild, the vulnerability could be leveraged by attackers to hijack user sessions, steal cookies, perform actions on behalf of users, or spread malware. The affected product is a web-based video player plugin, likely used in various websites to provide floating video playback functionality. The absence of a CVSS score indicates the need for a manual severity assessment. Given the nature of CSRF combined with stored XSS, the risk is significant, especially for websites with authenticated users and sensitive data. The vulnerability was published on December 16, 2024, and no patches or fixes have been linked yet, emphasizing the need for immediate attention from developers and administrators using this plugin.

Potential Impact

The impact of CVE-2024-54421 can be severe for organizations using the Floating Video Player plugin. Successful exploitation allows attackers to execute stored XSS attacks, which can lead to session hijacking, credential theft, unauthorized actions, and distribution of malware to site visitors. This compromises the confidentiality and integrity of user data and can degrade availability if malicious scripts disrupt normal operations. Organizations with high user interaction on affected websites are particularly vulnerable, as attackers can exploit authenticated sessions to escalate privileges or perform fraudulent transactions. The lack of authentication requirements and ease of exploitation via CSRF increase the threat level. Additionally, reputational damage and regulatory consequences may arise if user data is compromised. Since the vulnerability affects a widely used web component, the scope could be broad, impacting multiple industries including e-commerce, media, education, and corporate websites that embed this video player.

Mitigation Recommendations

To mitigate CVE-2024-54421, developers and administrators should immediately implement anti-CSRF tokens in all forms and state-changing requests within the Floating Video Player integration. Input validation and output encoding must be enforced rigorously to prevent stored XSS payloads from being injected or executed. Updating or patching the plugin once an official fix is released is critical. In the interim, consider disabling or removing the Floating Video Player plugin if it is not essential. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce XSS impact. Regular security audits and penetration testing focusing on CSRF and XSS vulnerabilities should be conducted. User sessions should be protected with secure, HttpOnly cookies and multi-factor authentication where possible to limit the damage from session hijacking. Monitoring web traffic for unusual requests indicative of CSRF attacks can help detect exploitation attempts early.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2024-12-02T12:06:23.394Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd75a4e6bfc5ba1df06b69

Added to database: 4/1/2026, 7:44:36 PM

Last enriched: 4/2/2026, 4:58:39 AM

Last updated: 4/4/2026, 8:18:07 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses