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

> Unauthenticated attackers can execute arbitrary SQL commands via the Client-Ip or X-Forwarded-For headers in the Huge-IT gallery-images plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 21 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-894j-rjhh-8rx8

## What is CVE-2016-11018?

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

### Official description

An issue was discovered in the Huge-IT gallery-images plugin before 1.9.0 for WordPress. The headers Client-Ip and X-Forwarded-For are prone to unauthenticated SQL injection. The affected file is gallery-images.php. The affected function is huge_it_image_gallery_ajax_callback().

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

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

It affects 1 product.


Products: Huge-It Image Gallery.

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

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

## Is CVE-2016-11018 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-7153](https://insights.sbomify.com/CVE-2014-7153/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-11018 is a critical SQL injection vulnerability in n/a, published on 21 Jan 2020. 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-11018 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-11018/ (Markdown: https://insights.sbomify.com/CVE-2016-11018/index.md)
```

## Sources

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

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