# CVE-2017-20096: WP-SpamFree Anti-Spam Plugin cross site scriting

> A cross-site scripting vulnerability in the WP-SpamFree Anti-Spam Plugin allows remote attackers to inject malicious scripts.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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:** 24 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-hjm7-73g4-786x

## What is CVE-2017-20096?

CVE-2017-20096 is a low-severity cross-site scripting vulnerability in unspecified WP-SpamFree Anti-Spam Plugin, published on 24 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic has been found in WP-SpamFree Anti-Spam Plugin 2.1.1.4. This affects an unknown part. The manipulation leads to basic cross site scripting. It is possible to initiate the attack remotely.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2017-20096?

It affects 1 product.


Products: Wp-Spamfree Anti-Spam Project Wp-Spamfree Anti-Spam.

## How do I fix CVE-2017-20096?

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

## Is CVE-2017-20096 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20096 and fix it if it is affected.

What it is: CVE-2017-20096 is a low-severity cross-site scripting vulnerability in unspecified WP-SpamFree Anti-Spam Plugin, published on 24 Jun 2022. 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-2017-20096 exists.

Affected product: unspecified WP-SpamFree Anti-Spam Plugin. 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-2017-20096/ (Markdown: https://insights.sbomify.com/CVE-2017-20096/index.md)
```

## Sources

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

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