# CVE-2023-29387: WordPress Manager for Icomoon Plugin <= 2.0 is vulnerable to Cross Site Scripting (XSS)

> Authenticated contributors can inject malicious scripts via the Manager for Icomoon plugin, potentially compromising user sessions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-qwhf-8wj5-jr35

## What is CVE-2023-29387?

CVE-2023-29387 is a medium-severity cross-site scripting vulnerability in Julien Crego Manager for Icomoon, published on 18 Aug 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Julien Crego Manager for Icomoon plugin <= 2.0 versions.

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

## Which versions are affected by CVE-2023-29387?

It affects 1 product.


Products: Juliencrego Manager for Icomoon.

## How do I fix CVE-2023-29387?

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

## Is CVE-2023-29387 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29387 and fix it if it is affected.

What it is: CVE-2023-29387 is a medium-severity cross-site scripting vulnerability in Julien Crego Manager for Icomoon, published on 18 Aug 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-29387 in the wild and no public exploit code.

Affected product: Julien Crego Manager for Icomoon. 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-2023-29387/ (Markdown: https://insights.sbomify.com/CVE-2023-29387/index.md)
```

## Sources

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

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