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

Plugin security history

History Log by click5 Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with History Log by click5, published between 2023 and 2025.

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

At a glance

Security Snapshot

3Total records
0Critical
1High
2Medium
0Low
0Informational
1Patched records
2Currently marked unpatched
2023-10-15First disclosure
2025-05-30Latest disclosure
3 of 3CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202311 records
202522 records

Severity Breakdown

SeverityRecordsShare
High133.3%
Medium266.7%

Vulnerability-Type Breakdown

SQL Injection

2 records66.7%

First: 2023. Latest: 2025.

Cross-Site Scripting

1 record33.3%

First: 2025. Latest: 2025.

Patch Status

Patched
1
Currently marked unpatched
2
Unknown status
0

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

Latest Known Patched Versions

  • 1.0.13

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.13History Log by click5 <= 1.0.13 - Authenticated (Subscriber+) Stored Cross-Site ScriptingMay 30, 2025Not suppliedMedium
*-1.0.13History Log by click5 <= 1.0.13 - Unauthenticated SQL InjectionMarch 31, 2025Not suppliedHigh
*-1.0.12History Log by click5 <= 1.0.12 - Authenticated(Administrator+) Time-Based Blind SQL InjectionOctober 15, 20231.0.13Medium

Selected source records

Latest Records

MediumCVE-2025-47598

History Log by click5 <= 1.0.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting

Published: May 30, 2025

Affected versions
*-1.0.13
Patched versions
Not supplied
Original Wordfence record
HighCVE-2025-31531

History Log by click5 <= 1.0.13 - Unauthenticated SQL Injection

Published: March 31, 2025

Affected versions
*-1.0.13
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2023-5082

History Log by click5 <= 1.0.12 - Authenticated(Administrator+) Time-Based Blind SQL Injection

Published: October 15, 2023

Affected versions
*-1.0.12
Patched versions
1.0.13
Original Wordfence record

Highest-Severity Records

HighCVE-2025-31531

History Log by click5 <= 1.0.13 - Unauthenticated SQL Injection

Published: March 31, 2025

Affected versions
*-1.0.13
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2023-5082

History Log by click5 <= 1.0.12 - Authenticated(Administrator+) Time-Based Blind SQL Injection

Published: October 15, 2023

Affected versions
*-1.0.12
Patched versions
1.0.13
Original Wordfence record
MediumCVE-2025-47598

History Log by click5 <= 1.0.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting

Published: May 30, 2025

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

Currently Marked Unpatched Records

MediumCVE-2025-47598

History Log by click5 <= 1.0.13 - Authenticated (Subscriber+) Stored Cross-Site Scripting

Published: May 30, 2025

Affected versions
*-1.0.13
Patched versions
Not supplied
Original Wordfence record
HighCVE-2025-31531

History Log by click5 <= 1.0.13 - Unauthenticated SQL Injection

Published: March 31, 2025

Affected versions
*-1.0.13
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