# CVE-2026-22660: FlaskBB Logic Flaw Authorization Group Deletion via Bulk AJAX Endpoint

> Authenticated administrators can delete built-in authorization groups due to a type mismatch, destroying the permission model and rendering the forum unusable.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-r9cf-jxr6-5h3r

## What is CVE-2026-22660?

CVE-2026-22660 is a high-severity vulnerability in flaskbb, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

FlaskBB through 2.2.0, fixed in commit a5da9a5, contains a logic flaw vulnerability that allows authenticated administrators to delete all built-in authorization groups by exploiting a type mismatch in the bulk delete protection check. The bulk AJAX endpoint in the management views compares received JSON integer group IDs against string literals, causing the protection check to always pass, which allows deletion of all six built-in groups and destroys the forum's permission model, potentially rendering the site unusable.

Weakness: CWE-697 (Incorrect Comparison)

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


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

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

## Is CVE-2026-22660 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22660 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22660 is a high-severity vulnerability in flaskbb, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22660 exists.

Affected product: flaskbb. 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-22660/ (Markdown: https://insights.sbomify.com/CVE-2026-22660/index.md)
```

## Sources

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

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