# CVE-2026-74932: WP Fastest Cache 0.9.0.3 - 1.5.0 - Unauthenticated Stored XSS via Host Header Cache Poisoning

> Unauthenticated attackers can poison cached pages via Host header injection, executing arbitrary JavaScript for all subsequent visitors.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-862p-vrqf-hqpw

## What is CVE-2026-74932?

CVE-2026-74932 is a high-severity cross-site scripting vulnerability in Unknown WP Fastest Cache, published on 25 Aug 2026. 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 Fastest Cache WordPress plugin before 1.5.1 does not validate the Host header before using it to build the URLs of the asset files it embeds in the pages it caches, and does not include that header in the cache key, allowing unauthenticated attackers to poison cached pages with references to a server they control and have arbitrary JavaScript run for every subsequent visitor.

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

## Which versions are affected by CVE-2026-74932?


## How do I fix CVE-2026-74932?

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

## Is CVE-2026-74932 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74932 and fix it if it is affected.

What it is: CVE-2026-74932 is a high-severity cross-site scripting vulnerability in Unknown WP Fastest Cache, published on 25 Aug 2026. 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-2026-74932 in the wild and no public exploit code.

Affected product: Unknown WP Fastest Cache. 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-2026-74932/ (Markdown: https://insights.sbomify.com/CVE-2026-74932/index.md)
```

## Sources

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

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