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

Plugin security history

BookingPress Appointment Booking Pro Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with BookingPress Appointment Booking Pro, published between 2026 and 2026.

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

At a glance

Security Snapshot

3Total records
1Critical
1High
1Medium
0Low
0Informational
3Patched records
0Currently marked unpatched
2026-05-21First disclosure
2026-07-06Latest disclosure
3 of 3CVE coverage

Use this history

Check and watch BookingPress Appointment Booking Pro.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
202633 records

Severity Breakdown

SeverityRecordsShare
Critical133.3%
High133.3%
Medium133.3%

Vulnerability-Type Breakdown

Arbitrary File Upload

1 record33.3%

First: 2026. Latest: 2026.

SQL Injection

1 record33.3%

First: 2026. Latest: 2026.

Missing Authorization

1 record33.3%

First: 2026. Latest: 2026.

Patch Status

Patched
3
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

  • 5.7.3
  • 5.7.2
  • 5.7

Affected-Version History

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

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-5.7.2BookingPress Pro <= 5.7.2 - Missing Authorization Unauthenticated Information ExposureJuly 6, 20265.7.3Medium
*-5.7.1BookingPress Appointment Booking Pro <= 5.7.1 - Unauthenticated SQL Injection via 'store_service_date' ParameterJune 30, 20265.7.2High
*-5.6BookingPress Pro <= 5.6 - Unauthenticated Arbitrary File Upload via Signature Custom FieldMay 21, 20265.7Critical

Selected source records

Latest Records

MediumCVE-2026-9830

BookingPress Pro <= 5.7.2 - Missing Authorization Unauthenticated Information Exposure

Published: July 6, 2026

Affected versions
*-5.7.2
Patched versions
5.7.3
Original Wordfence record
HighCVE-2026-11823

BookingPress Appointment Booking Pro <= 5.7.1 - Unauthenticated SQL Injection via 'store_service_date' Parameter

Published: June 30, 2026

Affected versions
*-5.7.1
Patched versions
5.7.2
Original Wordfence record
CriticalCVE-2026-6960

BookingPress Pro <= 5.6 - Unauthenticated Arbitrary File Upload via Signature Custom Field

Published: May 21, 2026

Affected versions
*-5.6
Patched versions
5.7
Original Wordfence record

Highest-Severity Records

CriticalCVE-2026-6960

BookingPress Pro <= 5.6 - Unauthenticated Arbitrary File Upload via Signature Custom Field

Published: May 21, 2026

Affected versions
*-5.6
Patched versions
5.7
Original Wordfence record
HighCVE-2026-11823

BookingPress Appointment Booking Pro <= 5.7.1 - Unauthenticated SQL Injection via 'store_service_date' Parameter

Published: June 30, 2026

Affected versions
*-5.7.1
Patched versions
5.7.2
Original Wordfence record
MediumCVE-2026-9830

BookingPress Pro <= 5.7.2 - Missing Authorization Unauthenticated Information Exposure

Published: July 6, 2026

Affected versions
*-5.7.2
Patched versions
5.7.3
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