CVE-2022-3402: The Log HTTP Requests plugin for WordPress is vulnerable to Stored Cross-Site Scripting via logged HTTP reques
CVE-2022-3402 is a medium-severity flaw (CVSS 6.1) affecting log http requests. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.8% (top 42%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2022-10-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-3402?
log http requests: upgrade to 1.3.2. Exact commands for each OS are on this page.
Is CVE-2022-3402 being exploited?
CVE-2022-3402 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-3402 affect?
CVE-2022-3402 affects log http requests. Severity is medium (CVSS 6.1). 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
How urgent is CVE-2022-3402?
Priority 36/100. No elevated risk signals yet.