# CVE-2023-0891: Stagtools < 2.3.7 - Contributor+ Stored XSS

> Contributors can inject malicious scripts via shortcode attributes in StagTools, leading to stored XSS attacks on WordPress sites.

- **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:** 2 May 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-mpr2-vg4h-vhcp

## What is CVE-2023-0891?

CVE-2023-0891 is a medium-severity cross-site scripting vulnerability in Unknown StagTools, published on 2 May 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 StagTools WordPress plugin before 2.3.7 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

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

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

It affects 1 product.


Products: Codestag Stagtools.

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

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

## Is CVE-2023-0891 being exploited?

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

## Other vulnerabilities in Unknown StagTools

- [CVE-2023-41868](https://insights.sbomify.com/CVE-2023-41868/): WordPress Stagtools Plugin <= 2.3.7 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0891 is a medium-severity cross-site scripting vulnerability in Unknown StagTools, published on 2 May 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-0891 exists.

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

## Sources

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

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