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-14557: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Drupal Facebook Pixel

0
Medium
VulnerabilityCVE-2025-14557cvecve-2025-14557cwe-79
Published: Wed Jan 14 2026 (01/14/2026, 18:40:34 UTC)
Source: CVE Database V5
Vendor/Project: Drupal
Product: Facebook Pixel

Description

CVE-2025-14557 is a stored Cross-site Scripting (XSS) vulnerability in the Drupal Facebook Pixel module versions 7. x-1. 0 through 7. x-1. 1. It arises from improper neutralization of input during web page generation, allowing attackers to inject malicious scripts that persist on affected sites. The vulnerability has a medium severity with a CVSS score of 4. 8 and does not require authentication but does require user interaction. While no known exploits are currently reported in the wild, exploitation could lead to session hijacking, defacement, or redirection to malicious sites. European organizations using the affected Drupal module should prioritize patching or mitigating this issue to prevent potential compromise.

AI-Powered Analysis

AILast updated: 01/21/2026, 20:44:02 UTC

Technical Analysis

CVE-2025-14557 is a stored Cross-site Scripting (XSS) vulnerability identified in the Drupal Facebook Pixel module, specifically affecting versions from 7.x-1.0 through 7.x-1.1. The vulnerability stems from improper neutralization of user-supplied input during the generation of web pages, classified under CWE-79. This flaw allows attackers to inject malicious JavaScript code that is stored persistently within the application, which is then executed in the browsers of users visiting the compromised pages. The attack vector is network-based with low attack complexity, requiring no privileges but some user interaction to trigger the payload. The vulnerability does not impact confidentiality, integrity, or availability directly but can be leveraged for session hijacking, phishing, or delivering further malware. The CVSS 4.0 vector indicates no user privileges are needed, but user interaction is required, and the scope is limited to the vulnerable component. No patches or known exploits are currently available, but the risk remains due to the widespread use of Drupal and its modules. The Facebook Pixel module is commonly used to integrate Facebook analytics and marketing tools into Drupal sites, making it a valuable target for attackers seeking to exploit trusted web properties.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to web applications using the Drupal Facebook Pixel module. Exploitation could lead to unauthorized script execution in users' browsers, enabling session hijacking, theft of sensitive information, or redirection to malicious websites. This can damage organizational reputation, lead to data breaches, and violate GDPR requirements related to data protection and user consent. E-commerce, government, and media websites are particularly at risk due to their reliance on user trust and data integrity. The vulnerability could also facilitate further attacks such as credential theft or malware distribution. Although the CVSS score is medium, the potential impact on user trust and compliance makes timely mitigation critical. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after public disclosure.

Mitigation Recommendations

European organizations should immediately audit their Drupal installations to identify the presence of the Facebook Pixel module versions 7.x-1.0 through 7.x-1.1. Since no official patches are currently available, organizations should consider the following mitigations: 1) Disable or remove the Facebook Pixel module if it is not essential. 2) Implement strict input validation and output encoding on all user-supplied data within the module to prevent script injection. 3) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4) Monitor web application logs for unusual input patterns or script injection attempts. 5) Educate users and administrators about the risks of XSS and encourage cautious interaction with suspicious content. 6) Stay updated with Drupal security advisories for forthcoming patches and apply them promptly. 7) Use web application firewalls (WAFs) with rules targeting XSS attacks to provide an additional layer of defense. These measures will help reduce the attack surface until an official patch is released.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
drupal
Date Reserved
2025-12-12T04:58:03.452Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6967e85ff809b25a98c7765e

Added to database: 1/14/2026, 7:02:55 PM

Last enriched: 1/21/2026, 8:44:02 PM

Last updated: 2/6/2026, 2:11:51 PM

Views: 23

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