# CVE-2022-0211: Shield Security < 13.0.6 - Admin+ Stored Cross-Site Scripting

> High-privilege users can inject malicious scripts via admin notes in the Shield Security plugin, bypassing HTML filtering restrictions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Feb 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5chx-62hx-4phc

## What is CVE-2022-0211?

CVE-2022-0211 is a medium-severity cross-site scripting vulnerability in Unknown Shield Security – Scanners, Security Hardening, Brute Force Protection & Firewall, published on 21 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Shield Security WordPress plugin before 13.0.6 does not sanitise and escape admin notes, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html is disallowed.

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

## Which versions are affected by CVE-2022-0211?

It affects 1 product.


Products: Getshieldsecurity Shield Security.

## How do I fix CVE-2022-0211?

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

## Is CVE-2022-0211 being exploited?

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

## Other vulnerabilities in Unknown Shield Security – Scanners, Security Hardening, Brute Force Protection & Firewall

- [CVE-2023-6989](https://insights.sbomify.com/CVE-2023-6989/): Shield Security – Smart Bot Blocking & Intrusion Prevention Security <= 18.5.9 - Unauthenticated Local File Inclusion (critical 9.8)
- [CVE-2023-0992](https://insights.sbomify.com/CVE-2023-0992/): Shield Security <= 17.0.17 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2024-22163](https://insights.sbomify.com/CVE-2024-22163/): WordPress Shield Security Plugin <= 18.5.7 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2024-7313](https://insights.sbomify.com/CVE-2024-7313/): Shield Security < 20.0.6 - Reflected XSS (medium 6.1)
- [CVE-2023-0993](https://insights.sbomify.com/CVE-2023-0993/): Shield Security <= 17.0.17 - Missing Authorization (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0211 and fix it if it is affected.

What it is: CVE-2022-0211 is a medium-severity cross-site scripting vulnerability in Unknown Shield Security – Scanners, Security Hardening, Brute Force Protection & Firewall, published on 21 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-0211 in the wild and no public exploit code.

Affected product: Unknown Shield Security – Scanners, Security Hardening, Brute Force Protection & Firewall. 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-2022-0211/ (Markdown: https://insights.sbomify.com/CVE-2022-0211/index.md)
```

## Sources

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

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