# CVE-2026-91024: Booking Manager < 2.1.21 - Author+ SQLi via ICS Import Feed UID (sync_gid)

> Authenticated authors can execute SQL injection via malicious iCalendar feed imports in the Booking Manager WordPress plugin.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-8743-f7m5-qxwx

## What is CVE-2026-91024?

CVE-2026-91024 is a medium-severity SQL injection vulnerability in Unknown Booking Manager, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Booking Manager  WordPress plugin before 2.1.21 does not sanitize and escape values taken from a fetched external iCalendar feed before using them in a SQL query, allowing authenticated users with Author-level access and above to perform SQL injection attacks by importing a feed they control.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-91024?


## How do I fix CVE-2026-91024?

No fix has been published for CVE-2026-91024 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91024 being exploited?

There is no known exploitation of CVE-2026-91024 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91024 and fix it if it is affected.

What it is: CVE-2026-91024 is a medium-severity SQL injection vulnerability in Unknown Booking Manager, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-91024 in the wild and no public exploit code.

Affected product: Unknown Booking Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91024/ (Markdown: https://insights.sbomify.com/CVE-2026-91024/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91024
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91024
- OSV: https://osv.dev/vulnerability/CVE-2026-91024

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91024/
Summaries are generated and may contain mistakes; the official description above is the record.