# CVE-2022-1028: WordPress Security < 4.2.1 - Admin+ Stored Cross-Site Scripting

> Administrators can inject malicious JavaScript via unsanitized settings in a WordPress security plugin, enabling stored XSS attacks in multisite environments.

- **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:** 27 Jun 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-p7f4-wpx9-f83x

## What is CVE-2022-1028?

CVE-2022-1028 is a medium-severity cross-site scripting vulnerability in Unknown WordPress Security – Firewall, Malware Scanner, Secure Login and Backup, published on 27 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The WordPress Security Firewall, Malware Scanner, Secure Login and Backup plugin before 4.2.1 does not sanitise and escape some of its settings, leading to malicious users with administrator privileges to store malicious Javascript code leading to Cross-Site Scripting attacks when unfiltered_html is disallowed (for example in multisite setup)

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

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

It affects 1 product.


Products: Miniorange Wordpress Security.

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

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

## Is CVE-2022-1028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1028 is a medium-severity cross-site scripting vulnerability in Unknown WordPress Security – Firewall, Malware Scanner, Secure Login and Backup, published on 27 Jun 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-1028 in the wild and no public exploit code.

Affected product: Unknown WordPress Security – Firewall, Malware Scanner, Secure Login and Backup. 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-1028/ (Markdown: https://insights.sbomify.com/CVE-2022-1028/index.md)
```

## Sources

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

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