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-2025-62746: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in CodeFlavors Featured Video for WordPress & VideographyWP

0
Medium
VulnerabilityCVE-2025-62746cvecve-2025-62746cwe-79
Published: Tue Dec 30 2025 (12/30/2025, 16:13:59 UTC)
Source: CVE Database V5
Vendor/Project: CodeFlavors
Product: Featured Video for WordPress & VideographyWP

Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CodeFlavors Featured Video for WordPress & VideographyWP allows Stored XSS.This issue affects Featured Video for WordPress & VideographyWP: from n/a through 1.0.18.

AI-Powered Analysis

AILast updated: 12/30/2025, 22:35:48 UTC

Technical Analysis

CVE-2025-62746 identifies a stored Cross-site Scripting (XSS) vulnerability in the CodeFlavors Featured Video for WordPress & VideographyWP plugin, affecting all versions up to 1.0.18. This vulnerability is classified under CWE-79, which involves improper neutralization of input during web page generation. Specifically, the plugin fails to sanitize or encode user-supplied input correctly before rendering it on web pages, allowing attackers to inject malicious JavaScript code that is stored persistently. When a victim visits a compromised page, the malicious script executes in their browser context, potentially leading to session hijacking, credential theft, or unauthorized actions on behalf of the user. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) indicates that the attack can be performed remotely over the network with low attack complexity, requires low privileges (authenticated user), and user interaction (clicking a link or visiting a page) is necessary. The scope is changed, meaning the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality, integrity, and availability, but with limited severity (partial loss). No patches are currently linked, and no active exploits have been reported, but the presence of stored XSS in a popular WordPress plugin poses a significant risk if exploited. The plugin is used primarily in WordPress environments to embed featured videos, making it attractive for attackers targeting content management systems.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized script execution within the context of authenticated users, potentially compromising sensitive information such as session tokens, personal data, or administrative credentials. This can facilitate further attacks like privilege escalation, data exfiltration, or site defacement. Organizations relying on WordPress for marketing, media, or e-commerce may suffer reputational damage and regulatory penalties under GDPR if personal data is exposed. The stored nature of the XSS increases risk since malicious payloads persist and affect multiple users. Given the widespread adoption of WordPress in Europe, especially in countries with large digital economies, the impact could be substantial if exploited at scale. The requirement for low privileges and user interaction lowers the barrier for exploitation, increasing risk in environments with many authenticated users. Additionally, compromised sites can be used to distribute malware or phishing campaigns, amplifying the threat.

Mitigation Recommendations

1. Monitor CodeFlavors and WordPress plugin repositories for official patches and apply them promptly once available. 2. Until patches are released, restrict plugin usage to trusted administrators and limit user roles that can input data into the plugin. 3. Implement strict input validation and output encoding on all user-supplied data related to the plugin, using security plugins or custom code to sanitize inputs. 4. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 5. Conduct regular security audits and penetration testing focusing on WordPress plugins and user input handling. 6. Educate users and administrators about the risks of clicking suspicious links or interacting with untrusted content. 7. Consider disabling or replacing the plugin with alternatives that have better security track records if immediate patching is not feasible. 8. Use Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting this plugin.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-10-21T14:59:50.024Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695450a4db813ff03e2be15d

Added to database: 12/30/2025, 10:22:28 PM

Last enriched: 12/30/2025, 10:35:48 PM

Last updated: 1/8/2026, 7:22:40 AM

Views: 12

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats