Skip to content
Noroxi

Advanced Booking Calendar

advanced-booking-calendar · plugin

Known security vulnerabilities for Advanced Booking Calendar. Find out in seconds which version runs on your site with WP Lens.

7 known vulnerabilities

2 critical · 4 exploitable without logging in · 1 with public exploit code · latest Dec 5, 2022

Before you install

Do not install

  • Closed on wordpress.org on Dec 1, 2022 (security issue); no updates will come.

Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.

This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.

Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector

Closed on wordpress.org

Removed from the directory on Dec 1, 2022 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.

wordpress.org status checked on Nov 13, 2026

Vulnerabilities

  • CVE-2022-45822unauthenticated≤ 1.7.1

    WordPress Advanced Booking Calendar Plugin <= 1.7.1 is vulnerable to SQL Injection

    Critical 9.8
  • CVE-2022-0694unauthenticated→ 1.7.0

    Advanced Booking Calendar < 1.7.0 - Unauthenticated SQL Injection

    Critical 9.8
  • CVE-2022-1006admin→ 1.7.1

    Advanced Booking Calendar < 1.7.1 - Admin+ SQLi

    High 7.2
  • CVE-2022-45824unauthenticated · needs a click≤ 1.7.1

    WordPress Advanced Booking Calendar Plugin <= 1.7.1 is vulnerable to Cross Site Request Forgery (CSRF)

    Medium 6.5
  • CVE-2022-1007unauthenticated · needs a click→ 1.7.1

    Advanced Booking Calendar < 1.7.1 - Reflected Cross-Site Scripting

    Medium 6.1
  • CVE-2021-24232login required→ 1.6.8

    Advanced Booking Calendar < 1.6.8 - Authenticated Reflected Cross-Site Scripting (XSS)

    Medium 5.4
  • CVE-2021-24225login required→ 1.6.7

    Advanced Booking Calendar < 1.6.7 - Authenticated Reflected Cross-Site Scripting (XSS)

    Medium 5.4

The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).

Exploited this week · every Monday

New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.

Your address is used only for this email and never shared.

← Back to directory