VulnerabilityPublished 14 Jan 2026

CVE-2025-14557: Drupal Facebook Pixel · XSS or 'Cross-site Scripting'

Affects Drupal Facebook PixelSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
DrupalFacebook Pixel	Affected >=7.x-1.0 <=7.x-1.1	Fixed in–

AI-suggested

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.

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.

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.

Summary

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.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 20:44 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats