# CVE-2017-20261: Joomla! Component Bargain Product VM3 1.0 SQL Injection

> Unauthenticated attackers can execute arbitrary SQL queries via the product_id parameter to extract sensitive database information from the Joomla Bargain Product VM3 component.

- **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:** 22 Jun 2026
- **Also known as:** GHSA-3r7g-gjfg-fgpr

## What is CVE-2017-20261?

CVE-2017-20261 is a high-severity SQL injection vulnerability in Weborange Bargain Product VM3, 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! Component Bargain Product VM3 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the product_id parameter. Attackers can supply crafted SQL statements in GET requests to the brainy and alice views to extract sensitive database information.

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

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

It affects 1 product.


Products: Weborange Bargain Product Vm3.

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

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

## Is CVE-2017-20261 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20261 is a high-severity SQL injection vulnerability in Weborange Bargain Product VM3, 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-20261 exists.

Affected product: Weborange Bargain Product VM3. 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-20261/ (Markdown: https://insights.sbomify.com/CVE-2017-20261/index.md)
```

## Sources

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

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