CVE-2024-4475: The WP Logs Book WordPress plugin through 1.0.1 does not have CSRF check when clearing logs, which could allow

Q: How do I fix CVE-2024-4475?

wp logs book: upgrade to newer than 1.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2024-4475 being exploited?

CVE-2024-4475 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-4475 affect?

CVE-2024-4475 affects wp logs book. Severity is medium (CVSS 4.3). The WP Logs Book WordPress plugin through 1.0.1 does not have CSRF check when clearing logs, which could allow attackers to make a logged in admin clear the logs them via a CSRF attack

Q: How urgent is CVE-2024-4475?

Priority 22/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

CVE-2024-4475 is a medium-severity flaw (CVSS 4.3) affecting wp logs book. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Logs Book WordPress plugin through 1.0.1 does not have CSRF check when clearing logs, which could allow attackers to make a logged in admin clear the logs them via a CSRF attack

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-06-21
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: onetarek

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-21 06:15 UTCPublished CVE record published
2026-06-17 08:01 UTCUpdated Record last modified

onetarek wp logs book UPGRADE

Affected: <= 1.0.1

Fixed in: newer than 1.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-logs-book || rpm -q wp-logs-book || wp-logs-book --version

2. UPGRADE to newer than 1.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-logs-book

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-logs-book

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2024-4475?

wp logs book: upgrade to newer than 1.0.1. Exact commands for each OS are on this page.

Is CVE-2024-4475 being exploited?

CVE-2024-4475 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-2024-4475 affect?

CVE-2024-4475 affects wp logs book. Severity is medium (CVSS 4.3). The WP Logs Book WordPress plugin through 1.0.1 does not have CSRF check when clearing logs, which could allow attackers to make a logged in admin clear the logs them via a CSRF attack

How urgent is CVE-2024-4475?

Priority 22/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-4477 MEDIUM 5.4 UPGRADE The WP Logs Book WordPress plugin through 1.0.1 does not sanitise and escape some of its log data before outpu
CVE-2024-4474 MEDIUM 4.3 UPGRADE The WP Logs Book WordPress plugin through 1.0.1 does not have CSRF check in place when updating its settings,

References

← Back to latest CVEs