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-8687: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in themelooks Enter Addons – Ultimate Template Builder for Elementor

0
Medium
VulnerabilityCVE-2025-8687cvecve-2025-8687cwe-79
Published: Sat Dec 13 2025 (12/13/2025, 08:21:14 UTC)
Source: CVE Database V5
Vendor/Project: themelooks
Product: Enter Addons – Ultimate Template Builder for Elementor

Description

The Enter Addons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Countdown and Image Comparison widgets in all versions up to, and including, 2.2.7 due to insufficient input sanitization and output escaping on user supplied attributes. 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, 08:50:56 UTC

Technical Analysis

CVE-2025-8687 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the Enter Addons – Ultimate Template Builder for Elementor WordPress plugin. This vulnerability exists in all versions up to and including 2.2.7 due to improper neutralization of input during web page generation. Specifically, the Countdown and Image Comparison widgets fail to adequately sanitize and escape user-supplied attributes, allowing authenticated users with contributor-level access or higher to inject arbitrary JavaScript code into pages. When other users visit these compromised pages, the injected scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or unauthorized actions on behalf of the victim. The vulnerability has a CVSS 3.1 base score of 6.4, reflecting medium severity, with an attack vector of network, low attack complexity, requiring privileges but no user interaction, and with a scope change indicating that the vulnerability affects resources beyond the initially vulnerable component. No public exploits are known at this time, but the risk remains significant due to the ease of exploitation by authenticated users and the potential impact on confidentiality and integrity of user data. The plugin is widely used in WordPress environments, which are prevalent in many European organizations for website management and content publishing.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality and integrity of web applications running WordPress with the affected plugin. Attackers with contributor-level access can embed malicious scripts that execute in the browsers of site visitors or administrators, potentially leading to session hijacking, theft of sensitive information, unauthorized actions, or defacement. This can damage organizational reputation, lead to data breaches, and cause compliance issues under regulations like GDPR. Since WordPress powers a significant portion of websites in Europe, including those of SMEs, public institutions, and enterprises, the impact can be widespread. Organizations with multiple content contributors or editors are particularly vulnerable, as these roles can be leveraged to exploit the flaw. The vulnerability does not affect availability directly but can indirectly cause service disruption through reputational damage or administrative lockout if attackers escalate privileges. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability is public.

Mitigation Recommendations

1. Immediately restrict contributor-level privileges to trusted users only, minimizing the risk of malicious script injection. 2. Implement strict input validation and output escaping on all user-supplied data within the affected widgets, either by applying custom filters or using security plugins that enforce sanitization. 3. Monitor and audit content changes made by contributors to detect suspicious script injections early. 4. Disable or remove the Countdown and Image Comparison widgets if they are not essential to reduce the attack surface. 5. Regularly update the Enter Addons plugin as soon as the vendor releases a security patch addressing this vulnerability. 6. Employ Web Application Firewalls (WAF) with rules to detect and block common XSS payloads targeting WordPress plugins. 7. Educate content contributors about the risks of injecting untrusted code or content. 8. Conduct periodic security assessments and penetration tests focusing on user input handling in WordPress environments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-08-06T21:20:01.797Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693d2749f35c2264d84723a5

Added to database: 12/13/2025, 8:43:53 AM

Last enriched: 12/13/2025, 8:50:56 AM

Last updated: 12/13/2025, 11:14:36 AM

Views: 7

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