# CVE-2022-1906: Copyright Proof <= 4.16 - Reflected Cross-Site-Scripting

> Reflected XSS in Copyright Proof plugin allows attackers to execute scripts via AJAX if a specific setting is enabled.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-93wh-rmxq-9c3v

## What is CVE-2022-1906?

CVE-2022-1906 is a medium-severity cross-site scripting vulnerability in Unknown Copyright Proof, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Copyright Proof WordPress plugin through 4.16 does not sanitise and escape a parameter before outputting it back via an AJAX action available to both unauthenticated and authenticated users, leading to a Reflected Cross-Site Scripting when a specific setting is enabled.

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

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

It affects 1 product.


Products: Digiprove Copyright Proof.

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

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

## Is CVE-2022-1906 being exploited?

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

Public exploit code:

- WordPress Copyright Proof <=4.16 - Cross-Site-Scripting (nuclei): http/cves/2022/CVE-2022-1906.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1906 is a medium-severity cross-site scripting vulnerability in Unknown Copyright Proof, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, 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-1906 exists.

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

## Sources

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

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