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-0350: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in badhonrocks Carousel Maker for Divi

0
Medium
VulnerabilityCVE-2025-0350cvecve-2025-0350cwe-79
Published: Sat Jan 25 2025 (01/25/2025, 09:22:46 UTC)
Source: CVE Database V5
Vendor/Project: badhonrocks
Product: Carousel Maker for Divi

Description

CVE-2025-0350 is a stored Cross-Site Scripting (XSS) vulnerability in the badhonrocks Carousel Maker for Divi WordPress plugin, affecting all versions up to 2. 0. 4. Authenticated users with contributor-level access or higher can inject malicious scripts via the Image Carousel and Logo Carousel features due to improper input sanitization and output escaping. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or further attacks. The vulnerability has a CVSS score of 6. 4, indicating medium severity, with no known exploits in the wild as of now. Mitigation requires patching or applying strict input validation and output encoding. Organizations using this plugin on WordPress sites should prioritize remediation to prevent exploitation. Countries with significant WordPress usage and active Divi plugin deployments are at higher risk.

AI-Powered Analysis

AILast updated: 02/25/2026, 23:49:37 UTC

Technical Analysis

CVE-2025-0350 identifies a stored Cross-Site Scripting (XSS) vulnerability in the badhonrocks Carousel Maker for Divi plugin, a popular WordPress plugin used to create image, logo, testimonial, and post carousels. The vulnerability arises from insufficient sanitization and escaping of user-supplied attributes in the Image Carousel and Logo Carousel components. Authenticated attackers with contributor-level privileges or higher can inject arbitrary JavaScript code into carousel elements. Because this is a stored XSS, the malicious payload is saved in the WordPress database and executed in the browsers of any users who visit the affected pages, including administrators and site visitors. The vulnerability does not require user interaction beyond visiting the compromised page and does not require elevated privileges beyond contributor access. The CVSS 3.1 score of 6.4 reflects a network attack vector with low attack complexity, requiring privileges but no user interaction, and impacts confidentiality and integrity with a scope change (potentially affecting other users). No patches or fixes have been publicly linked yet, and no known exploits are reported in the wild. The vulnerability is classified under CWE-79, which covers improper neutralization of input during web page generation leading to XSS.

Potential Impact

The impact of CVE-2025-0350 is significant for organizations using the affected plugin on WordPress sites. Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the affected site, potentially leading to session hijacking, theft of sensitive data such as cookies or credentials, defacement of website content, or redirection to malicious sites. Because the vulnerability is stored, the malicious code persists and affects all users who access the compromised pages, including administrators, increasing the risk of privilege escalation or further compromise. This can damage organizational reputation, lead to data breaches, and disrupt business operations. The requirement for contributor-level access limits exploitation to insiders or compromised accounts, but many WordPress sites grant such access to multiple users, increasing risk. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate it, as attackers may develop exploits rapidly once the vulnerability is public.

Mitigation Recommendations

To mitigate CVE-2025-0350, organizations should first check for updates from the plugin vendor and apply any available patches promptly. In the absence of official patches, administrators should restrict contributor-level access to trusted users only and audit existing user roles and permissions. Implementing Web Application Firewall (WAF) rules to detect and block suspicious script injections targeting carousel parameters can provide temporary protection. Site owners should also sanitize and validate all user inputs related to carousel content manually or via custom code to ensure no executable scripts are stored. Regular security scanning and monitoring for unusual activity or injected scripts in carousel content are recommended. Additionally, educating contributors about safe content practices and monitoring for account compromise can reduce exploitation risk. Finally, consider disabling or replacing the vulnerable plugin with a secure alternative if patching is not feasible.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-08T22:01:39.782Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6b67b7ef31ef0b555128

Added to database: 2/25/2026, 9:36:39 PM

Last enriched: 2/25/2026, 11:49:37 PM

Last updated: 2/26/2026, 6:17:54 AM

Views: 1

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