# CVE-2017-20277: Joomla JoomRecipe 1.0.4 Component Blind SQL Injection via search_author

> Attackers can extract database information via blind SQL injection in the JoomRecipe component's search_author parameter.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-qq25-hf4g-f5qf

## What is CVE-2017-20277?

CVE-2017-20277 is a high-severity SQL injection vulnerability in Joomboost Joomla JoomRecipe, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla JoomRecipe 1.0.4 component contains a blind SQL injection vulnerability in the search_author parameter on the search results page. Attackers can inject SQL code through POST requests to the search endpoint to extract database information using boolean-based blind SQL injection techniques.

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

## Which versions are affected by CVE-2017-20277?

It affects 1 product.


Products: Joomboost Joomla Joomrecipe.

## How do I fix CVE-2017-20277?

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

## Is CVE-2017-20277 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20277 and fix it if it is affected.

What it is: CVE-2017-20277 is a high-severity SQL injection vulnerability in Joomboost Joomla JoomRecipe, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20277 exists.

Affected product: Joomboost Joomla JoomRecipe. 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-2017-20277/ (Markdown: https://insights.sbomify.com/CVE-2017-20277/index.md)
```

## Sources

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

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