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

Plugin security history

WP Simple Booking Calendar Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with WP Simple Booking Calendar, published between 2021 and 2025.

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

At a glance

Security Snapshot

4Total records
0Critical
1High
3Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2021-08-06First disclosure
2025-04-16Latest disclosure
4 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202111 records
202311 records
202411 records
202511 records

Severity Breakdown

SeverityRecordsShare
High125%
Medium375%

Vulnerability-Type Breakdown

SQL Injection

1 record25%

First: 2021. Latest: 2021.

CSRF

1 record25%

First: 2023. Latest: 2023.

Cross-Site Scripting

1 record25%

First: 2024. Latest: 2024.

Missing Authorization

1 record25%

First: 2025. Latest: 2025.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

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

Latest Known Patched Versions

  • 2.0.14
  • 2.0.11
  • 2.0.8.5
  • 2.0.7

Affected-Version History

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

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.0.13WP Simple Booking Calendar <= 2.0.13 - Missing AuthorizationApril 16, 20252.0.14Medium
*-2.0.10WP Simple Booking Calendar <= 2.0.10 - Reflected Cross-Site ScriptingSeptember 12, 20242.0.11Medium
*-2.0.8.4WP Simple Booking Calendar <= 2.0.8.4 - Cross-Site Request ForgeryDecember 27, 20232.0.8.5Medium
*-2.0.6WP Simple Booking Calendar <= 2.0.6 - Authenticated SQL InjectionAugust 6, 20212.0.7High

Selected source records

Latest Records

MediumCVE-2025-39541

WP Simple Booking Calendar <= 2.0.13 - Missing Authorization

Published: April 16, 2025

Affected versions
*-2.0.13
Patched versions
2.0.14
Original Wordfence record
MediumCVE-2024-8663

WP Simple Booking Calendar <= 2.0.10 - Reflected Cross-Site Scripting

Published: September 12, 2024

Affected versions
*-2.0.10
Patched versions
2.0.11
Original Wordfence record
MediumCVE-2023-51525

WP Simple Booking Calendar <= 2.0.8.4 - Cross-Site Request Forgery

Published: December 27, 2023

Affected versions
*-2.0.8.4
Patched versions
2.0.8.5
Original Wordfence record
HighCVE-2021-24726

WP Simple Booking Calendar <= 2.0.6 - Authenticated SQL Injection

Published: August 6, 2021

Affected versions
*-2.0.6
Patched versions
2.0.7
Original Wordfence record

Highest-Severity Records

HighCVE-2021-24726

WP Simple Booking Calendar <= 2.0.6 - Authenticated SQL Injection

Published: August 6, 2021

Affected versions
*-2.0.6
Patched versions
2.0.7
Original Wordfence record
MediumCVE-2024-8663

WP Simple Booking Calendar <= 2.0.10 - Reflected Cross-Site Scripting

Published: September 12, 2024

Affected versions
*-2.0.10
Patched versions
2.0.11
Original Wordfence record
MediumCVE-2023-51525

WP Simple Booking Calendar <= 2.0.8.4 - Cross-Site Request Forgery

Published: December 27, 2023

Affected versions
*-2.0.8.4
Patched versions
2.0.8.5
Original Wordfence record
MediumCVE-2025-39541

WP Simple Booking Calendar <= 2.0.13 - Missing Authorization

Published: April 16, 2025

Affected versions
*-2.0.13
Patched versions
2.0.14
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