# CVE-2026-102788: Joomla Extension - balbooa.com - Unauthenticated SQL injection in Gridbox < 2.20.4.2


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-hqjq-crc6-5fp3

## What is CVE-2026-102788?

CVE-2026-102788 is a critical vulnerability in balbooa.com Gridbox extension for Joomla, published on 27 Oct 2026. 

### Official description

Joomla Extension - balbooa.com - Unauthenticated SQL injection in Gridbox < 2.20.4.2 - On store product list pages, the value of the sort-by URL parameter is retrieved using a string filter and passed directly to GridboxHelper::getBlogPosts(). When the parameter does not match known sorting keys, it is prefixed with a table alias and inserted into the ORDER BY clause without checking against an allowlist

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

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


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

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

## Is CVE-2026-102788 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102788 is a critical vulnerability in balbooa.com Gridbox extension for Joomla, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-102788 in the wild and no public exploit code.

Affected product: balbooa.com Gridbox extension for Joomla. 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-102788/ (Markdown: https://insights.sbomify.com/CVE-2026-102788/index.md)
```

## Sources

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

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