# CVE-2022-41132: WordPress Ezoic plugin <= 2.8.8 - Unauthenticated Plugin Settings Change Leading To Stored XSS Vulnerability

> Unauthenticated attackers can modify plugin settings to inject malicious scripts, leading to stored XSS and potential site compromise.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Nov 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-j8fm-fpfm-m64h

## What is CVE-2022-41132?

CVE-2022-41132 is a medium-severity cross-site scripting vulnerability in Ezoic (WordPress plugin), published on 17 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unauthenticated Plugin Settings Change Leading To Stored XSS Vulnerability in Ezoic plugin <= 2.8.8 on WordPress.

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

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

It affects 1 product.


Products: Ezoic Ezoic.

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

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

## Is CVE-2022-41132 being exploited?

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

## Other vulnerabilities in Ezoic (WordPress plugin)

- [CVE-2022-41315](https://insights.sbomify.com/CVE-2022-41315/): WordPress Ezoic plugin <= 2.8.8 - Auth. Stored Cross-Site Scripting (XSS) vulnerability (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41132 is a medium-severity cross-site scripting vulnerability in Ezoic (WordPress plugin), published on 17 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-41132 in the wild and no public exploit code.

Affected product: Ezoic (WordPress plugin). 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-41132/ (Markdown: https://insights.sbomify.com/CVE-2022-41132/index.md)
```

## Sources

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

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