Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

WP Logs Book Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with WP Logs Book, published between 2024 and 2024.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

3Total records
0Critical
1High
2Medium
0Low
0Informational
0Patched records
3Currently marked unpatched
2024-05-31First disclosure
2024-05-31Latest disclosure
3 of 3CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202433 records

Severity Breakdown

SeverityRecordsShare
High133.3%
Medium266.7%

Vulnerability-Type Breakdown

CSRF

2 records66.7%

First: 2024. Latest: 2024.

Cross-Site Scripting

1 record33.3%

First: 2024. Latest: 2024.

Patch Status

Patched
0
Currently marked unpatched
3
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

No patched version values are available for this software in the current Production Feed records.

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-1.0.1WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log ClearingMay 31, 2024Not suppliedMedium
*-1.0.1WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log DisablingMay 31, 2024Not suppliedMedium
*-1.0.1WP Logs Book <= 1.0.1 - Unauthenticated Stored Cross-Site ScriptingMay 31, 2024Not suppliedHigh

Selected source records

Latest Records

HighCVE-2024-4477

WP Logs Book <= 1.0.1 - Unauthenticated Stored Cross-Site Scripting

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4474

WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log Disabling

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4475

WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log Clearing

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record

Highest-Severity Records

HighCVE-2024-4477

WP Logs Book <= 1.0.1 - Unauthenticated Stored Cross-Site Scripting

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4474

WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log Disabling

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4475

WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log Clearing

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record

Currently Marked Unpatched Records

HighCVE-2024-4477

WP Logs Book <= 1.0.1 - Unauthenticated Stored Cross-Site Scripting

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4474

WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log Disabling

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-4475

WP Logs Book <= 1.0.1 - Cross-Site Request Forgery to Log Clearing

Published: May 31, 2024

Affected versions
*-1.0.1
Patched versions
Not supplied
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory