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-2024-5611: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in jetmonsters Stratum – Elementor Widgets

0
Medium
VulnerabilityCVE-2024-5611cvecve-2024-5611cwe-79
Published: Sat Jun 15 2024 (06/15/2024, 09:43:51 UTC)
Source: CVE Database V5
Vendor/Project: jetmonsters
Product: Stratum – Elementor Widgets

Description

CVE-2024-5611 is a stored Cross-Site Scripting (XSS) vulnerability in the Stratum – Elementor Widgets WordPress plugin, specifically affecting the Countdown widget's 'label_years' attribute. Authenticated users with Contributor-level access or higher can inject malicious scripts that execute when any user views the compromised page. The vulnerability arises from insufficient input sanitization and output escaping, allowing persistent script injection. The CVSS score is 6. 4 (medium severity), reflecting network exploitability with low complexity and no user interaction required. Although no known exploits are reported in the wild, the vulnerability poses risks to site integrity and user confidentiality. Organizations using this plugin should prioritize patching or apply strict input validation and role restrictions to mitigate risk. Countries with significant WordPress usage and e-commerce presence are most likely affected.

AI-Powered Analysis

AILast updated: 02/26/2026, 02:42:25 UTC

Technical Analysis

CVE-2024-5611 identifies a stored Cross-Site Scripting (XSS) vulnerability in the Stratum – Elementor Widgets plugin for WordPress, affecting all versions up to and including 1.4.1. The vulnerability is located in the 'label_years' attribute of the Countdown widget, where insufficient input sanitization and output escaping allow authenticated users with Contributor-level privileges or higher to inject arbitrary JavaScript code. This malicious code is stored persistently and executed whenever any user accesses the affected page, potentially compromising user sessions, stealing cookies, or performing unauthorized actions on behalf of users. The vulnerability leverages CWE-79, a common web application weakness related to improper neutralization of input during web page generation. The CVSS 3.1 score of 6.4 reflects that the attack vector is network-based, requires low attack complexity, privileges at the Contributor level, no user interaction, and impacts confidentiality and integrity with a scope change. No patches are currently linked, and no known exploits have been observed in the wild, but the vulnerability's presence in a widely used WordPress plugin makes it a notable risk. The plugin's popularity in website building and e-commerce contexts increases the potential attack surface. Mitigation requires either updating the plugin once a patch is released or implementing strict input validation and limiting Contributor-level access to trusted users. Monitoring for suspicious activity and employing Web Application Firewalls (WAFs) with XSS detection rules can also help reduce risk.

Potential Impact

The primary impact of CVE-2024-5611 is the compromise of confidentiality and integrity within affected WordPress sites. An attacker with Contributor-level access can inject persistent malicious scripts that execute in the browsers of site visitors and administrators, potentially leading to session hijacking, credential theft, defacement, or unauthorized actions performed with the victim's privileges. This can erode user trust, damage brand reputation, and expose sensitive data. Since the vulnerability does not affect availability directly, denial-of-service is less of a concern. However, the ability to execute arbitrary scripts can facilitate further attacks, including phishing or malware distribution. Organizations relying on the Stratum – Elementor Widgets plugin for critical business websites, especially e-commerce or customer-facing portals, face increased risk of data breaches and compliance violations. The ease of exploitation by authenticated users means insider threats or compromised contributor accounts can be leveraged. The scope of affected systems is broad given WordPress's global market share and the plugin's usage, potentially impacting thousands of websites worldwide.

Mitigation Recommendations

1. Monitor the vendor's official channels for a security patch and apply updates immediately once available. 2. Until a patch is released, restrict Contributor-level access to trusted users only, minimizing the risk of malicious script injection. 3. Implement strict input validation and output encoding on the 'label_years' attribute if custom code or filters are used. 4. Deploy a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting WordPress plugins. 5. Regularly audit user roles and permissions to ensure least privilege principles are enforced. 6. Conduct security awareness training for contributors to recognize and avoid unsafe content practices. 7. Use security plugins that can scan for injected scripts or anomalous content within WordPress pages. 8. Monitor logs and user activity for suspicious behavior indicative of exploitation attempts. 9. Consider disabling or replacing the vulnerable plugin if immediate patching is not feasible. 10. Backup website data regularly to enable recovery in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-06-03T20:04:08.443Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6bedb7ef31ef0b55caae

Added to database: 2/25/2026, 9:38:53 PM

Last enriched: 2/26/2026, 2:42:25 AM

Last updated: 2/26/2026, 11:19:31 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