# CVE-2023-4798: User Avatar - Reloaded < 1.2.2 - Contributor+ Stored XSS

> Low-privileged users can inject malicious scripts via shortcode attributes, leading to stored XSS attacks in the User Avatar plugin.

- **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:** 16 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-cv5w-p79v-vvxq

## What is CVE-2023-4798?

CVE-2023-4798 is a medium-severity cross-site scripting vulnerability in Unknown User Avatar, published on 16 Oct 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 User Avatar WordPress plugin before 1.2.2 does not properly sanitize and escape certain of its shortcodes attributes, which could allow relatively low-privileged users like contributors to conduct Stored XSS attacks.

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

It affects 1 product.


Products: Wpexperts User Avatar-Reloaded.

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

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

## Is CVE-2023-4798 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4798 is a medium-severity cross-site scripting vulnerability in Unknown User Avatar, published on 16 Oct 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-4798 in the wild and no public exploit code.

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

## Sources

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

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