# CVE-2023-33207: WordPress Stop Referrer Spam Plugin <= 1.3.0 is vulnerable to Cross Site Request Forgery (CSRF)

> Attackers can trick users into performing unwanted actions in the Stop Referrer Spam WordPress plugin via CSRF.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 13 Nov 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-rwp9-5vgw-8w4x

## What is CVE-2023-33207?

CVE-2023-33207 is a medium-severity vulnerability in Krzysztof Wielogórski Stop Referrer Spam, published on 13 Nov 2023. 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

Cross-Site Request Forgery (CSRF) vulnerability in Krzysztof Wielogórski Stop Referrer Spam plugin <= 1.3.0 versions.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wielogorski Stop Referrer Spam.

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

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

## Is CVE-2023-33207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33207 is a medium-severity vulnerability in Krzysztof Wielogórski Stop Referrer Spam, published on 13 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-33207 in the wild and no public exploit code.

Affected product: Krzysztof Wielogórski Stop Referrer Spam. 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-33207/ (Markdown: https://insights.sbomify.com/CVE-2023-33207/index.md)
```

## Sources

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

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