Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2022-1006: SQL Injection in Advanced Booking Calendar WordPress plugin calendar editing

Published Apr 11, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.2High · v3.1
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildReported193 exploitation records in Mallory
Vendor
Elbtide
IdentifiersCVE-2022-1006CWE-89 · Improper Neutralization of Special…

CVE-2022-1006 is a SQL injection vulnerability in the Advanced Booking Calendar WordPress plugin before version 1.7.1. The vulnerability is caused by improper sanitization and escaping of the id parameter when editing calendars. An authenticated high-privilege user, such as an administrator, can supply crafted input to this parameter, resulting in SQL queries being modified and attacker-controlled SQL being executed against the backend database.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a high-privilege authenticated attacker to perform SQL injection against the WordPress site's database through the calendar editing functionality. Depending on database permissions and application behavior, this can enable unauthorized reading or modification of database contents and may compromise the integrity of plugin or site data.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to WordPress administrative functionality to only fully trusted users, reduce the number of high-privilege accounts, monitor administrative actions involving the plugin's calendar editing features, and use database least-privilege principles to limit the impact of SQL injection. Temporary mitigation may also include disabling the plugin until it can be updated.

Remediation

Patch, then assume compromise.

Upgrade the Advanced Booking Calendar WordPress plugin to version 1.7.1 or later, which addresses the improper sanitization and escaping of the id parameter in the calendar editing workflow.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ElbtideAdvanced Booking Calendarapplication
FAQ

Frequently asked questions

Is CVE-2022-1006 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-1006?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-1006.
Is there a patch for CVE-2022-1006?
Upgrade the Advanced Booking Calendar WordPress plugin to version 1.7.1 or later, which addresses the improper sanitization and escaping of the id parameter in the calendar editing workflow.
What products are affected by CVE-2022-1006?
Elbtide Advanced Booking Calendar.
How severe is CVE-2022-1006?
CVE-2022-1006 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 1.5% (75th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.