CVE-2024-12520: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in reader87 Dominion – Domain Checker for WPBakery
CVE-2024-12520 is a stored cross-site scripting (XSS) vulnerability in the Dominion – Domain Checker for WPBakery WordPress plugin, affecting all versions up to 2. 2. 2. The flaw arises from improper input sanitization and output escaping in the 'dominion_shortcodes_domain_search_6' shortcode, allowing authenticated users with contributor-level or higher privileges to inject malicious scripts. These scripts execute in the context of any user who views the compromised page, potentially leading to session hijacking, privilege escalation, or defacement. The vulnerability has a CVSS 3. 1 base score of 6. 4, indicating medium severity, with network attack vector, low attack complexity, and no user interaction required. No known public exploits have been reported yet. Organizations using this plugin should prioritize patching or applying mitigations to prevent exploitation.
AI Analysis
Technical Summary
CVE-2024-12520 is a stored cross-site scripting vulnerability classified under CWE-79 found in the Dominion – Domain Checker for WPBakery plugin for WordPress. This vulnerability affects all versions up to and including 2.2.2. The root cause is insufficient sanitization and escaping of user-supplied input in the 'dominion_shortcodes_domain_search_6' shortcode. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript code into pages generated by the plugin. When other users visit these compromised pages, the malicious scripts execute in their browsers, potentially allowing attackers to steal session cookies, perform actions on behalf of users, or deface the website. The vulnerability is exploitable remotely over the network without user interaction, with low attack complexity, but requires authentication with contributor or higher privileges. The CVSS 3.1 score of 6.4 reflects a medium severity impact, with confidentiality and integrity impacts rated as low but no impact on availability. No patches or official fixes have been published yet, and no known exploits are reported in the wild. This vulnerability highlights the importance of proper input validation and output encoding in WordPress plugins, especially those that accept user input in shortcodes. Organizations using this plugin should monitor for updates, restrict contributor access, and consider additional security controls to mitigate risk.
Potential Impact
The primary impact of this vulnerability is the potential for stored cross-site scripting attacks, which can compromise the confidentiality and integrity of user sessions and data. Attackers can hijack user sessions, steal authentication tokens, or perform unauthorized actions with the privileges of the victim user. This can lead to account takeover, data leakage, or defacement of websites. Since the vulnerability requires contributor-level authentication, the risk is somewhat mitigated by the need for an attacker to have or obtain such access, but insider threats or compromised contributor accounts increase risk. The scope includes any WordPress site using the affected plugin versions, which may be widespread given the popularity of WPBakery and domain checking plugins. The vulnerability does not affect availability directly but can degrade user trust and site reputation. Organizations with high-value targets or sensitive user data are at greater risk of consequential damage from exploitation.
Mitigation Recommendations
1. Immediately restrict contributor-level and higher access to trusted users only, and review existing user privileges to minimize risk exposure. 2. Monitor for and apply vendor patches or updates as soon as they become available; if no patch exists, consider disabling the vulnerable shortcode or the entire plugin temporarily. 3. Implement Web Application Firewall (WAF) rules to detect and block malicious script injections targeting the vulnerable shortcode parameters. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 5. Conduct regular security audits and code reviews of plugins, especially those accepting user input in shortcodes or forms. 6. Educate site administrators and contributors about the risks of XSS and safe content input practices. 7. Consider using security plugins that sanitize shortcode inputs or provide additional input validation layers. 8. Monitor site logs for unusual activity indicative of exploitation attempts.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, India, France, Brazil, Netherlands, Japan
CVE-2024-12520: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in reader87 Dominion – Domain Checker for WPBakery
Description
CVE-2024-12520 is a stored cross-site scripting (XSS) vulnerability in the Dominion – Domain Checker for WPBakery WordPress plugin, affecting all versions up to 2. 2. 2. The flaw arises from improper input sanitization and output escaping in the 'dominion_shortcodes_domain_search_6' shortcode, allowing authenticated users with contributor-level or higher privileges to inject malicious scripts. These scripts execute in the context of any user who views the compromised page, potentially leading to session hijacking, privilege escalation, or defacement. The vulnerability has a CVSS 3. 1 base score of 6. 4, indicating medium severity, with network attack vector, low attack complexity, and no user interaction required. No known public exploits have been reported yet. Organizations using this plugin should prioritize patching or applying mitigations to prevent exploitation.
AI-Powered Analysis
Technical Analysis
CVE-2024-12520 is a stored cross-site scripting vulnerability classified under CWE-79 found in the Dominion – Domain Checker for WPBakery plugin for WordPress. This vulnerability affects all versions up to and including 2.2.2. The root cause is insufficient sanitization and escaping of user-supplied input in the 'dominion_shortcodes_domain_search_6' shortcode. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript code into pages generated by the plugin. When other users visit these compromised pages, the malicious scripts execute in their browsers, potentially allowing attackers to steal session cookies, perform actions on behalf of users, or deface the website. The vulnerability is exploitable remotely over the network without user interaction, with low attack complexity, but requires authentication with contributor or higher privileges. The CVSS 3.1 score of 6.4 reflects a medium severity impact, with confidentiality and integrity impacts rated as low but no impact on availability. No patches or official fixes have been published yet, and no known exploits are reported in the wild. This vulnerability highlights the importance of proper input validation and output encoding in WordPress plugins, especially those that accept user input in shortcodes. Organizations using this plugin should monitor for updates, restrict contributor access, and consider additional security controls to mitigate risk.
Potential Impact
The primary impact of this vulnerability is the potential for stored cross-site scripting attacks, which can compromise the confidentiality and integrity of user sessions and data. Attackers can hijack user sessions, steal authentication tokens, or perform unauthorized actions with the privileges of the victim user. This can lead to account takeover, data leakage, or defacement of websites. Since the vulnerability requires contributor-level authentication, the risk is somewhat mitigated by the need for an attacker to have or obtain such access, but insider threats or compromised contributor accounts increase risk. The scope includes any WordPress site using the affected plugin versions, which may be widespread given the popularity of WPBakery and domain checking plugins. The vulnerability does not affect availability directly but can degrade user trust and site reputation. Organizations with high-value targets or sensitive user data are at greater risk of consequential damage from exploitation.
Mitigation Recommendations
1. Immediately restrict contributor-level and higher access to trusted users only, and review existing user privileges to minimize risk exposure. 2. Monitor for and apply vendor patches or updates as soon as they become available; if no patch exists, consider disabling the vulnerable shortcode or the entire plugin temporarily. 3. Implement Web Application Firewall (WAF) rules to detect and block malicious script injections targeting the vulnerable shortcode parameters. 4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers. 5. Conduct regular security audits and code reviews of plugins, especially those accepting user input in shortcodes or forms. 6. Educate site administrators and contributors about the risks of XSS and safe content input practices. 7. Consider using security plugins that sanitize shortcode inputs or provide additional input validation layers. 8. Monitor site logs for unusual activity indicative of exploitation attempts.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2024-12-11T13:48:50.769Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6e40b7ef31ef0b59bb3f
Added to database: 2/25/2026, 9:48:48 PM
Last enriched: 2/26/2026, 3:59:40 AM
Last updated: 2/26/2026, 7:32:33 AM
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25191: Uncontrolled Search Path Element in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-23703: Incorrect default permissions in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-1311: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in bearsthemes Worry Proof Backup
HighFinding Signal in the Noise: Lessons Learned Running a Honeypot with AI Assistance [Guest Diary], (Tue, Feb 24th)
MediumCVE-2026-2506: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in motahar1 EM Cost Calculator
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.