# CVE-2023-47513: WordPress ARI Stream Quiz – WordPress Quizzes Builder plugin <= 1.3.2 - Content Injection vulnerability

> An attacker can inject malicious scripts into the ARI Stream Quiz WordPress plugin, potentially executing code in the context of other users.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-vf9v-cp45-wpq2

## What is CVE-2023-47513?

CVE-2023-47513 is a medium-severity cross-site scripting vulnerability in ARI Stream Quiz, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in ARI Soft ARI Stream Quiz allows Code Injection.This issue affects ARI Stream Quiz: from n/a through 1.3.2.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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


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

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

## Is CVE-2023-47513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47513 is a medium-severity cross-site scripting vulnerability in ARI Stream Quiz, published on 4 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-47513 in the wild and no public exploit code.

Affected product: ARI Stream Quiz. 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-47513/ (Markdown: https://insights.sbomify.com/CVE-2023-47513/index.md)
```

## Sources

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

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