Is Log HTTP Requests safe?

No known vulnerability affects the current version (1.5.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Oct 5, 2022.

Checked 4 days ago against the WPVulnerability database, for version 1.5.0.

How it’s looked after

Last release: Nov 11, 2025 (11 months ago)
Releases in the last year: 0
Tested up to: WordPress 6.8.12 (current: 7.1)
Active installs: 2K+

1 known vulnerability

1 medium

None affects the current version.

Every known vulnerability in Log HTTP Requests

Newest first, with any that affect the current version at the top.

medium
Stored Cross-Site Scripting
Fixed in 1.3.2 · CVE-2022-3402 · Oct 5, 2022 · Wordfence

Questions about Log HTTP Requests’s security

Is Log HTTP Requests safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Log HTTP Requests updated: most attacks target sites that haven’t updated.

Does Log HTTP Requests have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Log HTTP Requests up to date.

Is Log HTTP Requests still maintained?

Its last release was 11 months ago. No support threads were opened in the last two months.

Is Log HTTP Requests compatible with the latest WordPress?

Log HTTP Requests’s readme says it’s tested up to WordPress 6.8.12, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.