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-3811: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ThemeNectar Salient Shortcodes

0
Medium
VulnerabilityCVE-2024-3811cvecve-2024-3811cwe-79
Published: Sat May 18 2024 (05/18/2024, 05:40:02 UTC)
Source: CVE Database V5
Vendor/Project: ThemeNectar
Product: Salient Shortcodes

Description

CVE-2024-3811 is a stored cross-site scripting (XSS) vulnerability in the ThemeNectar Salient Shortcodes WordPress plugin, affecting all versions up to 1. 5. 3. It arises from improper input sanitization and output escaping on the 'icon' shortcode's user-supplied attributes. Authenticated users with contributor-level access or higher can inject malicious scripts that execute whenever any user views the compromised page. The vulnerability has a CVSS 3. 1 score of 6. 4, indicating medium severity, with potential impacts on confidentiality and integrity but no direct availability impact. Exploitation requires authentication but no user interaction beyond viewing the injected page. No known exploits are currently reported in the wild.

AI-Powered Analysis

AILast updated: 02/26/2026, 06:26:03 UTC

Technical Analysis

CVE-2024-3811 is a stored cross-site scripting (XSS) vulnerability identified in the ThemeNectar Salient Shortcodes plugin for WordPress, specifically affecting the 'icon' shortcode. The flaw exists due to insufficient sanitization and escaping of user-supplied attributes, allowing authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. When other users access these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or data theft. The vulnerability affects all versions up to and including 1.5.3. The CVSS 3.1 base score of 6.4 reflects that the attack vector is network-based, requires low attack complexity, and privileges at the contributor level, with no user interaction needed. The scope is changed because the vulnerability can affect other users beyond the attacker. While no known exploits are currently reported, the vulnerability poses a significant risk in multi-user WordPress environments where contributors can add content. The lack of output escaping and input validation in the shortcode's implementation is the root cause, highlighting a common web application security weakness (CWE-79).

Potential Impact

The primary impact of this vulnerability is on the confidentiality and integrity of user data within affected WordPress sites. Attackers can execute arbitrary scripts in the context of the victim's browser, potentially stealing cookies, session tokens, or performing actions on behalf of other users. This can lead to account takeover, defacement, or unauthorized data access. Since the vulnerability requires contributor-level access, it is less likely to be exploited by external unauthenticated attackers but poses a significant insider threat or risk from compromised contributor accounts. The vulnerability does not directly affect availability but can indirectly disrupt site operations through malicious payloads or reputation damage. Organizations relying on this plugin for content management or marketing may face data breaches or loss of user trust if exploited. The scope includes all users who view the injected content, expanding the potential victim pool.

Mitigation Recommendations

To mitigate CVE-2024-3811, organizations should immediately update the Salient Shortcodes plugin to a patched version once available. In the absence of an official patch, administrators should restrict contributor-level permissions to trusted users only and audit existing content for suspicious shortcode usage. Implementing a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the 'icon' shortcode parameters can reduce risk. Additionally, site owners should enforce Content Security Policy (CSP) headers to limit script execution sources. Regularly scanning the site for injected scripts and monitoring user activity logs can help detect exploitation attempts. Developers maintaining the plugin should apply proper input validation and output encoding on all shortcode attributes to prevent script injection. Finally, educating contributors about secure content practices and limiting plugin usage to essential features can further reduce attack surface.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-04-15T13:17:17.423Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c9db7ef31ef0b566d78

Added to database: 2/25/2026, 9:41:49 PM

Last enriched: 2/26/2026, 6:26:03 AM

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