# CVE-2016-1000123: SQL injection in n/a

> Unauthenticated attackers can execute arbitrary SQL commands via the Huge-IT Video Gallery plugin for Joomla, potentially accessing or modifying database content.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2j5g-w3c2-pj99

## What is CVE-2016-1000123?

CVE-2016-1000123 is a critical SQL injection vulnerability in n/a, published on 6 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated SQL Injection in Huge-IT Video Gallery v1.0.9 for Joomla

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

## Which versions are affected by CVE-2016-1000123?

It affects 1 product.


Products: Huge-It Video Gallery.

## How do I fix CVE-2016-1000123?

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

## Is CVE-2016-1000123 being exploited?

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

Public exploit code:

- Joomla! Component Huge-IT Video Gallery 1.0.9 - SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1000123 and fix it if it is affected.

What it is: CVE-2016-1000123 is a critical SQL injection vulnerability in n/a, published on 6 Oct 2016. 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-2016-1000123 in the wild and no public exploit code.

Affected product: n/a. 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-2016-1000123/ (Markdown: https://insights.sbomify.com/CVE-2016-1000123/index.md)
```

## Sources

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

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