CVE-2026-0693: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in arnoesterhuizen Allow HTML in Category Descriptions
The Allow HTML in Category Descriptions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via category descriptions in all versions up to, and including, 1.2.4. This is due to the plugin unconditionally removing the `wp_kses_data` output filter for term_description, link_description, link_notes, and user_description fields without checking user capabilities. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in category descriptions that will execute whenever a user accesses a page where the category description is displayed. This only affects multi-site installations and installations where unfiltered_html has been disabled.
AI Analysis
Technical Summary
CVE-2026-0693 is a stored cross-site scripting vulnerability found in the WordPress plugin 'Allow HTML in Category Descriptions' by arnoesterhuizen, affecting all versions up to and including 1.2.4. The root cause is the plugin's unconditional removal of the wp_kses_data output filter on fields such as term_description, link_description, link_notes, and user_description without verifying the user's capability to input HTML safely. This flaw allows authenticated users with administrator-level privileges or higher to inject arbitrary JavaScript into category descriptions. When any user accesses a page displaying these category descriptions, the injected scripts execute in their browser context, potentially leading to session hijacking, defacement, or other client-side attacks. The vulnerability specifically impacts WordPress multisite installations or those where the unfiltered_html capability is disabled, as these configurations normally restrict HTML input to trusted users. The attack vector requires high privileges (administrator or above), no user interaction is needed once the script is injected, and the scope is limited to sites using this plugin in the specified configurations. The CVSS 3.1 base score is 4.4, indicating medium severity due to the combination of network attack vector, high attack complexity, and required privileges. No known exploits have been reported in the wild as of the publication date. The vulnerability highlights the risk of improper input sanitization and capability checks in WordPress plugins that extend HTML input functionality.
Potential Impact
For European organizations, the impact of CVE-2026-0693 is primarily on the confidentiality and integrity of user sessions and data within affected WordPress multisite environments. Successful exploitation could allow an attacker with administrator privileges to execute malicious scripts in the browsers of site visitors or other administrators, potentially leading to session hijacking, unauthorized actions, or defacement. While availability is not directly impacted, the reputational damage and potential data leakage could be significant for organizations relying on WordPress for public-facing or internal multisite deployments. The requirement for administrator-level access limits the risk to insider threats or compromised admin accounts, but given the widespread use of WordPress in Europe, especially in government, education, and media sectors, the vulnerability could be leveraged in targeted attacks. Organizations with strict content policies disabling unfiltered_html are particularly vulnerable, as the plugin bypasses these restrictions. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as the vulnerability is publicly disclosed.
Mitigation Recommendations
European organizations should take the following specific actions to mitigate CVE-2026-0693: 1) Immediately audit WordPress multisite installations for the presence of the 'Allow HTML in Category Descriptions' plugin and assess usage of category descriptions containing HTML. 2) Restrict administrator privileges to trusted personnel and enforce strong authentication mechanisms to reduce the risk of privilege abuse. 3) Temporarily disable or remove the vulnerable plugin until a patched version is released. 4) Monitor category descriptions and other affected fields for suspicious or unexpected HTML or JavaScript content, using automated scanning tools where possible. 5) Implement Content Security Policy (CSP) headers to limit the impact of potential XSS payloads by restricting script execution sources. 6) Educate administrators about the risks of injecting untrusted HTML content and enforce strict content input policies. 7) Stay updated with vendor advisories and apply patches promptly once available. 8) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block malicious scripts in category descriptions. These measures go beyond generic advice by focusing on the specific plugin, multisite configurations, and administrative controls.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Belgium, Sweden, Austria
CVE-2026-0693: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in arnoesterhuizen Allow HTML in Category Descriptions
Description
The Allow HTML in Category Descriptions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via category descriptions in all versions up to, and including, 1.2.4. This is due to the plugin unconditionally removing the `wp_kses_data` output filter for term_description, link_description, link_notes, and user_description fields without checking user capabilities. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in category descriptions that will execute whenever a user accesses a page where the category description is displayed. This only affects multi-site installations and installations where unfiltered_html has been disabled.
AI-Powered Analysis
Technical Analysis
CVE-2026-0693 is a stored cross-site scripting vulnerability found in the WordPress plugin 'Allow HTML in Category Descriptions' by arnoesterhuizen, affecting all versions up to and including 1.2.4. The root cause is the plugin's unconditional removal of the wp_kses_data output filter on fields such as term_description, link_description, link_notes, and user_description without verifying the user's capability to input HTML safely. This flaw allows authenticated users with administrator-level privileges or higher to inject arbitrary JavaScript into category descriptions. When any user accesses a page displaying these category descriptions, the injected scripts execute in their browser context, potentially leading to session hijacking, defacement, or other client-side attacks. The vulnerability specifically impacts WordPress multisite installations or those where the unfiltered_html capability is disabled, as these configurations normally restrict HTML input to trusted users. The attack vector requires high privileges (administrator or above), no user interaction is needed once the script is injected, and the scope is limited to sites using this plugin in the specified configurations. The CVSS 3.1 base score is 4.4, indicating medium severity due to the combination of network attack vector, high attack complexity, and required privileges. No known exploits have been reported in the wild as of the publication date. The vulnerability highlights the risk of improper input sanitization and capability checks in WordPress plugins that extend HTML input functionality.
Potential Impact
For European organizations, the impact of CVE-2026-0693 is primarily on the confidentiality and integrity of user sessions and data within affected WordPress multisite environments. Successful exploitation could allow an attacker with administrator privileges to execute malicious scripts in the browsers of site visitors or other administrators, potentially leading to session hijacking, unauthorized actions, or defacement. While availability is not directly impacted, the reputational damage and potential data leakage could be significant for organizations relying on WordPress for public-facing or internal multisite deployments. The requirement for administrator-level access limits the risk to insider threats or compromised admin accounts, but given the widespread use of WordPress in Europe, especially in government, education, and media sectors, the vulnerability could be leveraged in targeted attacks. Organizations with strict content policies disabling unfiltered_html are particularly vulnerable, as the plugin bypasses these restrictions. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as the vulnerability is publicly disclosed.
Mitigation Recommendations
European organizations should take the following specific actions to mitigate CVE-2026-0693: 1) Immediately audit WordPress multisite installations for the presence of the 'Allow HTML in Category Descriptions' plugin and assess usage of category descriptions containing HTML. 2) Restrict administrator privileges to trusted personnel and enforce strong authentication mechanisms to reduce the risk of privilege abuse. 3) Temporarily disable or remove the vulnerable plugin until a patched version is released. 4) Monitor category descriptions and other affected fields for suspicious or unexpected HTML or JavaScript content, using automated scanning tools where possible. 5) Implement Content Security Policy (CSP) headers to limit the impact of potential XSS payloads by restricting script execution sources. 6) Educate administrators about the risks of injecting untrusted HTML content and enforce strict content input policies. 7) Stay updated with vendor advisories and apply patches promptly once available. 8) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block malicious scripts in category descriptions. These measures go beyond generic advice by focusing on the specific plugin, multisite configurations, and administrative controls.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-07T20:58:33.120Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69901aebc9e1ff5ad8689318
Added to database: 2/14/2026, 6:49:15 AM
Last enriched: 2/14/2026, 7:18:40 AM
Last updated: 2/21/2026, 12:21:36 AM
Views: 23
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-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
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.