# CVE-2026-0693: Cross-site scripting in Allow HTML in Category Descriptions

> Administrators can inject arbitrary scripts into category descriptions, leading to stored XSS in multi-site or restricted HTML environments.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f4qw-9xx8-rwgr

## What is CVE-2026-0693?

CVE-2026-0693 is a medium-severity cross-site scripting vulnerability in arnoesterhuizen Allow HTML in Category Descriptions, published on 14 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-0693?


## How do I fix CVE-2026-0693?

No fix has been published for CVE-2026-0693 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0693 being exploited?

There is no known exploitation of CVE-2026-0693 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0693 and fix it if it is affected.

What it is: CVE-2026-0693 is a medium-severity cross-site scripting vulnerability in arnoesterhuizen Allow HTML in Category Descriptions, published on 14 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0693 in the wild and no public exploit code.

Affected product: arnoesterhuizen Allow HTML in Category Descriptions. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0693/ (Markdown: https://insights.sbomify.com/CVE-2026-0693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0693
- OSV: https://osv.dev/vulnerability/CVE-2026-0693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0693/
Summaries are generated and may contain mistakes; the official description above is the record.