Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using the Log HTTP Requests plugin through version 1.3.1. Malicious request data can be stored by the plugin and later run as script when a user views the affected log page. The business risk is mainly admin-session compromise or unauthorized actions within WordPress.
Executive priority
Treat this as a moderate-priority WordPress hygiene issue. It is not listed as known exploited in the provided sources, but it can affect administrator sessions and should be fixed during the next maintenance window.
Technical view
CVE-2022-3402 is stored cross-site scripting in logged HTTP request handling. The CVE description attributes it to insufficient input sanitization and output escaping. The vector is network-accessible with low complexity, no privileges required, but user interaction is required. CVSS 3.1 score is 6.1.
Likely exposure
Exposure is limited to WordPress installations with Log HTTP Requests version 1.3.1 or earlier. Sites where administrators or privileged users review plugin-captured request logs have the clearest practical exposure.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The described attack requires stored malicious content and later viewing of the affected page by a user, such as an administrator.
Researcher notes
The provided CVE affected metadata is inconsistent with the narrative: it lists version "0" with default status unaffected, while the description says versions up to 1.3.1 are vulnerable. Use the Wordfence advisory and WordPress plugin changelog to confirm exact fixed version before reporting closure.
Mitigation direction
- Inventory WordPress sites for Log HTTP Requests plugin usage.
- Upgrade beyond version 1.3.1 where vendor guidance confirms a fixed release.
- Disable or remove the plugin if it is not operationally required.
- Restrict WordPress administrator access to trusted users and networks.
- Review vendor advisory and WordPress plugin changelog before deployment.
Validation and detection
- Check installed plugin version on each WordPress site.
- Confirm whether administrators can access stored HTTP request logs.
- Review the referenced WordPress changeset for sanitization and escaping changes.
- Verify the vendor or plugin page identifies a fixed release.
- Look for suspicious script-like content in stored request log data.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-3402 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/b12b0a2a-3c3c-4d9c-a404-c8f170638e31?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2770821%40log-http-requests&new=2770821%40log-http-requests&sfp_email=&sfph_mail=CVE reference
- https://wordpress.org/plugins/log-http-requests/#developersCVE reference
- https://www.wordfence.com/vulnerability-advisories-continued/#CVE-2022-3402CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.