# CVE-2026-74804: Joomla Extension - yootheme.com - Unauthenticated SQL injection in Zoo < 4.1.64

> Unauthenticated attackers can execute arbitrary SQL commands via the filter_type parameter in the Zoo extension for Joomla.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-v9gw-jh22-6wqh

## What is CVE-2026-74804?

CVE-2026-74804 is a critical SQL injection vulnerability in yootheme.com Zoo extension for Joomla, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla Extension - yootheme.com - Unauthenticated SQL injection in ItemController::element() in Zoo < 4.1.64 - The filter_type request value is interpolated into the query as a.type = "..." and the type_filter array as a.type IN ("..."), with no quoting or escaping.

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

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


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

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

## Is CVE-2026-74804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74804 is a critical SQL injection vulnerability in yootheme.com Zoo extension for Joomla, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74804 in the wild and no public exploit code.

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

## Sources

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

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