# CVE-2022-3402: Log HTTP Requests <= 1.3.1 - Stored Cross-Site Scripting

> Unauthenticated attackers can inject arbitrary web scripts via logged HTTP requests, potentially leading to code execution or account takeover when administrators view the logs.

- **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:** 28 Oct 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j8m4-m9gj-6wrm

## What is CVE-2022-3402?

CVE-2022-3402 is a medium-severity cross-site scripting vulnerability in mgibbs189 Log HTTP Requests, published on 28 Oct 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 Log HTTP Requests plugin for WordPress is vulnerable to Stored Cross-Site Scripting via logged HTTP requests in versions up to, and including, 1.3.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers who can trick a site's administrator into performing an action like clicking on a link, or an authenticated user with access to a page that sends a request using user-supplied data via the server, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

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

It affects 1 product.


Products: Facetwp Log Http Requests.

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

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

## Is CVE-2022-3402 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3402 is a medium-severity cross-site scripting vulnerability in mgibbs189 Log HTTP Requests, published on 28 Oct 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: There is no known exploitation of CVE-2022-3402 in the wild and no public exploit code.

Affected product: mgibbs189 Log HTTP Requests. 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-3402/ (Markdown: https://insights.sbomify.com/CVE-2022-3402/index.md)
```

## Sources

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

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