CVE-2022-1006: The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the id parameter when

Q: How do I fix CVE-2022-1006?

advanced booking calendar: upgrade to 1.7.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-1006 being exploited?

CVE-2022-1006 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1006 affect?

CVE-2022-1006 affects advanced booking calendar. Severity is high (CVSS 7.2). The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the id parameter when editing Calendars, which could allow high privilege users such as admin to perform SQL injection attacks

Q: How urgent is CVE-2022-1006?

Priority 49/100. High severity; Public exploit reference

This month

HIGH 7.2UPGRADE

CVE-2022-1006 is a high-severity flaw (CVSS 7.2) affecting advanced booking calendar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the id parameter when editing Calendars, which could allow high privilege users such as admin to perform SQL injection attacks

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-04-11
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: elbtide

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-04-11 15:15 UTCPublished CVE record published
2026-06-17 04:21 UTCUpdated Record last modified

elbtide advanced booking calendar UPGRADE

Affected: < 1.7.1

Fixed in: 1.7.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy advanced-booking-calendar || rpm -q advanced-booking-calendar || advanced-booking-calendar --version

2. UPGRADE to 1.7.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade advanced-booking-calendar

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade advanced-booking-calendar

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1006?

advanced booking calendar: upgrade to 1.7.1. Exact commands for each OS are on this page.

Is CVE-2022-1006 being exploited?

CVE-2022-1006 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1006 affect?

CVE-2022-1006 affects advanced booking calendar. Severity is high (CVSS 7.2). The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the id parameter when editing Calendars, which could allow high privilege users such as admin to perform SQL injection attacks

How urgent is CVE-2022-1006?

Priority 49/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-45824 MEDIUM 5.4 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in Advanced Booking Calendar plugin <= 1.7.1 on WordPress.
CVE-2022-45822 CRITICAL 10.0 UPGRADE Unauth
CVE-2022-1007 MEDIUM 6.1 UPGRADE The Advanced Booking Calendar WordPress plugin before 1.7.1 does not sanitise and escape the room parameter be
CVE-2022-0694 CRITICAL 9.8 UPGRADE The Advanced Booking Calendar WordPress plugin before 1.7.0 does not validate and escape the calendar paramete
CVE-2021-24232 MEDIUM 5.4 UPGRADE The Advanced Booking Calendar WordPress plugin before 1.6.8 does not sanitise the license error message when o

References

← Back to latest CVEs