CVE-2022-3408: CWE-79 Cross-Site Scripting (XSS) in Unknown WP Word Count
The WP Word Count WordPress plugin through 3.2.3 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed.
AI Analysis
Technical Summary
CVE-2022-3408 is a medium-severity vulnerability affecting the WP Word Count WordPress plugin version 3.2.3 and earlier. The vulnerability is a Cross-Site Scripting (XSS) flaw categorized under CWE-79. It arises because the plugin fails to properly sanitize and escape certain settings inputs. This deficiency allows users with high privileges, such as administrators, to inject malicious scripts into the plugin's settings interface. Notably, this XSS can be executed even when the WordPress 'unfiltered_html' capability is disabled, which normally restricts the ability to post unfiltered HTML content. The attack vector requires network access (AV:N), low attack complexity (AC:L), and high privileges (PR:H) with user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. The impact on confidentiality and integrity is low, with no impact on availability. Exploitation would typically involve tricking an admin user into interacting with a crafted input or interface element that triggers the malicious script, potentially leading to session hijacking, privilege escalation, or unauthorized actions within the WordPress admin environment. There are no known exploits in the wild, and no official patches have been linked, indicating that mitigation may rely on plugin updates or manual code review and sanitization by site administrators.
Potential Impact
For European organizations using WordPress sites with the WP Word Count plugin version 3.2.3 or earlier, this vulnerability poses a risk primarily to site integrity and confidentiality. An attacker with admin-level access could leverage this XSS flaw to execute arbitrary scripts, potentially stealing session cookies, modifying site content, or escalating privileges further. While the vulnerability requires high privileges to exploit, insider threats or compromised admin accounts could be leveraged. The impact is particularly relevant for organizations with sensitive or regulated data hosted on WordPress platforms, such as government agencies, financial institutions, healthcare providers, and e-commerce businesses in Europe. Exploitation could lead to data leakage, defacement, or unauthorized administrative actions, undermining trust and compliance with data protection regulations like GDPR. However, the lack of known active exploitation and the medium severity rating suggest the threat is moderate but should not be ignored, especially in environments where WordPress plugins are widely used and administrative access is shared or less tightly controlled.
Mitigation Recommendations
European organizations should take the following specific actions to mitigate this vulnerability: 1) Immediately identify and inventory WordPress sites using the WP Word Count plugin version 3.2.3 or earlier. 2) Upgrade the plugin to the latest available version where the vulnerability is patched or apply vendor-provided fixes if available. 3) If no patch exists, implement manual input sanitization and escaping for plugin settings fields by modifying the plugin code or using security plugins that enforce input validation. 4) Restrict administrative access strictly to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of compromised admin accounts. 5) Regularly audit WordPress user roles and permissions to minimize the number of high-privilege users. 6) Monitor WordPress logs and web traffic for unusual activity that could indicate attempted exploitation, such as unexpected script injections or admin interface anomalies. 7) Educate administrators about the risks of XSS and the importance of cautious interaction with plugin settings and external inputs. 8) Consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting WordPress admin interfaces.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2022-3408: CWE-79 Cross-Site Scripting (XSS) in Unknown WP Word Count
Description
The WP Word Count WordPress plugin through 3.2.3 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Cross-Site Scripting attacks even when unfiltered_html is disallowed.
AI-Powered Analysis
Technical Analysis
CVE-2022-3408 is a medium-severity vulnerability affecting the WP Word Count WordPress plugin version 3.2.3 and earlier. The vulnerability is a Cross-Site Scripting (XSS) flaw categorized under CWE-79. It arises because the plugin fails to properly sanitize and escape certain settings inputs. This deficiency allows users with high privileges, such as administrators, to inject malicious scripts into the plugin's settings interface. Notably, this XSS can be executed even when the WordPress 'unfiltered_html' capability is disabled, which normally restricts the ability to post unfiltered HTML content. The attack vector requires network access (AV:N), low attack complexity (AC:L), and high privileges (PR:H) with user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. The impact on confidentiality and integrity is low, with no impact on availability. Exploitation would typically involve tricking an admin user into interacting with a crafted input or interface element that triggers the malicious script, potentially leading to session hijacking, privilege escalation, or unauthorized actions within the WordPress admin environment. There are no known exploits in the wild, and no official patches have been linked, indicating that mitigation may rely on plugin updates or manual code review and sanitization by site administrators.
Potential Impact
For European organizations using WordPress sites with the WP Word Count plugin version 3.2.3 or earlier, this vulnerability poses a risk primarily to site integrity and confidentiality. An attacker with admin-level access could leverage this XSS flaw to execute arbitrary scripts, potentially stealing session cookies, modifying site content, or escalating privileges further. While the vulnerability requires high privileges to exploit, insider threats or compromised admin accounts could be leveraged. The impact is particularly relevant for organizations with sensitive or regulated data hosted on WordPress platforms, such as government agencies, financial institutions, healthcare providers, and e-commerce businesses in Europe. Exploitation could lead to data leakage, defacement, or unauthorized administrative actions, undermining trust and compliance with data protection regulations like GDPR. However, the lack of known active exploitation and the medium severity rating suggest the threat is moderate but should not be ignored, especially in environments where WordPress plugins are widely used and administrative access is shared or less tightly controlled.
Mitigation Recommendations
European organizations should take the following specific actions to mitigate this vulnerability: 1) Immediately identify and inventory WordPress sites using the WP Word Count plugin version 3.2.3 or earlier. 2) Upgrade the plugin to the latest available version where the vulnerability is patched or apply vendor-provided fixes if available. 3) If no patch exists, implement manual input sanitization and escaping for plugin settings fields by modifying the plugin code or using security plugins that enforce input validation. 4) Restrict administrative access strictly to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of compromised admin accounts. 5) Regularly audit WordPress user roles and permissions to minimize the number of high-privilege users. 6) Monitor WordPress logs and web traffic for unusual activity that could indicate attempted exploitation, such as unexpected script injections or admin interface anomalies. 7) Educate administrators about the risks of XSS and the importance of cautious interaction with plugin settings and external inputs. 8) Consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting WordPress admin interfaces.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- WPScan
- Date Reserved
- 2022-10-06T00:00:00.000Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d981bc4522896dcbd9e11
Added to database: 5/21/2025, 9:08:43 AM
Last enriched: 7/5/2025, 4:11:24 PM
Last updated: 7/31/2025, 6:11:17 AM
Views: 14
Related Threats
CVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighCVE-2025-9088: Stack-based Buffer Overflow in Tenda AC20
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.