# CVE-2022-3739: WP Best Quiz <= 1.0 - Author+ Stored XSS

> Authors can inject malicious scripts via unsanitized parameters in WP Best Quiz, potentially compromising user sessions or site integrity.

- **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 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-fv65-3wh4-c445

## What is CVE-2022-3739?

CVE-2022-3739 is a medium-severity cross-site scripting vulnerability in Unknown WP Best Quiz, published on 16 Jan 2024. 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 WP Best Quiz WordPress plugin through 1.0 does not sanitize and escape some parameters, which could allow users with a role as low as Author to perform Cross-Site Scripting attacks.

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

## Which versions are affected by CVE-2022-3739?

It affects 1 product.


Products: Subina Wp Best Quiz.

## How do I fix CVE-2022-3739?

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

## Is CVE-2022-3739 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3739 and fix it if it is affected.

What it is: CVE-2022-3739 is a medium-severity cross-site scripting vulnerability in Unknown WP Best Quiz, published on 16 Jan 2024. 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-2022-3739 exists.

Affected product: Unknown WP Best 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-2022-3739/ (Markdown: https://insights.sbomify.com/CVE-2022-3739/index.md)
```

## Sources

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

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