# CVE-2023-2579: InventoryPress <= 1.7 - Author+ Stored XSS

> Authors can inject malicious scripts into InventoryPress settings, leading to stored XSS attacks against other users.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 17 Jul 2023
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-j4gg-9rwv-9gxg

## What is CVE-2023-2579?

CVE-2023-2579 is a medium-severity cross-site scripting vulnerability in Unknown InventoryPress, published on 17 Jul 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

The InventoryPress WordPress plugin through 1.7 does not sanitise and escape some of its settings, which could allow users with the role of author and above to perform Stored Cross-Site Scripting attacks.

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

It affects 1 product.


Products: Inventorypress Project Inventorypress.

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

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

## Is CVE-2023-2579 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2579 exists.

Public exploit code:

- PoC for CVE-2023-2579 (github_poc): https://github.com/0xn4d/poc-cve-xss-inventory-press-plugin

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2579 is a medium-severity cross-site scripting vulnerability in Unknown InventoryPress, published on 17 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2579 exists.

Affected product: Unknown InventoryPress. 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-2579/ (Markdown: https://insights.sbomify.com/CVE-2023-2579/index.md)
```

## Sources

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

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