# CVE-2011-5266: SQL injection in n/a

> Attackers can bypass SQL injection filters in Imperva SecureSphere WAF, allowing malicious queries to reach backend databases.

- **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:** 8 Jan 2020
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5fh4-5wpg-mhxh

## What is CVE-2011-5266?

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

### Official description

Imperva SecureSphere Web Application Firewall (WAF) before 12-august-2010 allows SQL injection filter bypass.

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

## Which versions are affected by CVE-2011-5266?

It affects 1 product.


Products: Imperva Securesphere Web Application Firewall.

## How do I fix CVE-2011-5266?

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

## Is CVE-2011-5266 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4887](https://insights.sbomify.com/CVE-2011-4887/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-0767](https://insights.sbomify.com/CVE-2011-0767/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5266 and fix it if it is affected.

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

## Sources

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

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