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-12109: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in mahethekiller Header Footer Script Adder – Insert Code in Header, Body & Footer

0
Medium
VulnerabilityCVE-2025-12109cvecve-2025-12109cwe-79
Published: Sat Dec 13 2025 (12/13/2025, 04:31:32 UTC)
Source: CVE Database V5
Vendor/Project: mahethekiller
Product: Header Footer Script Adder – Insert Code in Header, Body & Footer

Description

The Header Footer Script Adder – Insert Code in Header, Body & Footer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the script adder present in posts in all versions up to, and including, 2.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

AILast updated: 12/13/2025, 05:08:19 UTC

Technical Analysis

CVE-2025-12109 is a stored Cross-Site Scripting (XSS) vulnerability identified in the WordPress plugin 'Header Footer Script Adder – Insert Code in Header, Body & Footer' developed by mahethekiller. This plugin allows users to insert custom scripts into the header, body, or footer sections of WordPress pages. The vulnerability exists due to improper neutralization of input during web page generation (CWE-79), specifically insufficient sanitization and escaping of user-supplied input before rendering it in posts. Authenticated attackers with Contributor-level access or higher can exploit this flaw by injecting arbitrary JavaScript code into posts or pages. When other users visit these compromised pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, credential theft, or unauthorized actions performed on behalf of the victim. The vulnerability affects all plugin versions up to and including 2.0.5. The CVSS v3.1 base score is 6.4, indicating medium severity, with an attack vector over the network, low attack complexity, privileges required at the contributor level, no user interaction needed, and a scope change due to impact on other components. No known public exploits or patches are currently available, increasing the urgency for administrators to implement interim mitigations. The vulnerability's presence in a widely used WordPress plugin poses a significant risk to websites that rely on this plugin for script management, especially in environments with multiple contributors.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized script execution on their WordPress sites, compromising the confidentiality and integrity of user data. Attackers could steal session cookies, perform actions on behalf of legitimate users, or deliver further malware payloads. This is particularly concerning for organizations with multi-user content management workflows, such as media companies, educational institutions, and e-commerce platforms, where contributors have posting rights. The exploitation could damage brand reputation, lead to data breaches involving personal data protected under GDPR, and cause operational disruptions. Since the vulnerability does not affect availability directly, denial-of-service impacts are minimal, but the scope change in CVSS indicates potential compromise beyond the initial component. The lack of patches and known exploits suggests a window of exposure, emphasizing the need for proactive defense. European organizations with public-facing WordPress sites using this plugin are at risk, especially those in countries with high WordPress adoption and stringent data protection regulations.

Mitigation Recommendations

1. Immediately audit and restrict user roles to limit Contributor-level access only to trusted personnel. 2. Implement strict content review and approval workflows before publishing posts or pages containing user-generated scripts. 3. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious script injections targeting this plugin. 4. Monitor website content for unexpected script tags or suspicious payloads, using automated scanning tools tailored for XSS detection. 5. Disable or remove the 'Header Footer Script Adder' plugin if it is not essential, or replace it with a more secure alternative that properly sanitizes inputs. 6. Stay alert for official patches or updates from the plugin vendor and apply them promptly once released. 7. Educate content contributors about the risks of injecting untrusted code and enforce strict input validation policies. 8. Use Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts on the website. 9. Regularly back up website data to enable quick recovery in case of compromise. 10. Conduct penetration testing focused on XSS vulnerabilities to identify and remediate similar issues proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-23T13:46:20.322Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693cef62d977419e584a4fe2

Added to database: 12/13/2025, 4:45:22 AM

Last enriched: 12/13/2025, 5:08:19 AM

Last updated: 12/15/2025, 1:38:44 AM

Views: 14

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats