# CVE-2021-34665: WP SEO Tags <= 2.2.7 Reflected Cross-Site Scripting

> Attackers can inject arbitrary web scripts via the saq_txt_the_filter parameter in the WP SEO Tags plugin, potentially compromising user sessions.

- **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:** 16 Aug 2021
- **Updated:** 23 May 2025
- **Also known as:** GHSA-3xgh-9rw3-wpjw

## What is CVE-2021-34665?

CVE-2021-34665 is a medium-severity cross-site scripting vulnerability in WP SEO Tags, published on 16 Aug 2021. 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 WP SEO Tags WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the saq_txt_the_filter parameter in the ~/wp-seo-tags.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 2.2.7.

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

## Which versions are affected by CVE-2021-34665?

It affects 1 product.


Products: Wp Seo Tags Project Wp Seo Tags.

## How do I fix CVE-2021-34665?

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

## Is CVE-2021-34665 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34665 and fix it if it is affected.

What it is: CVE-2021-34665 is a medium-severity cross-site scripting vulnerability in WP SEO Tags, published on 16 Aug 2021. 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-2021-34665 in the wild and no public exploit code.

Affected product: WP SEO Tags. 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-2021-34665/ (Markdown: https://insights.sbomify.com/CVE-2021-34665/index.md)
```

## Sources

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

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