# CVE-2016-4905: SQL injection in WP-OliveCart

> Administrators can execute arbitrary SQL commands in WP-OliveCart plugins, potentially compromising database integrity and confidentiality.

- **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:** 22 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2rx2-6g92-c889

## What is CVE-2016-4905?

CVE-2016-4905 is a critical SQL injection vulnerability in WP-OliveCart, published on 22 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the WP-OliveCart versions prior to 3.1.3 and WP-OliveCartPro versions prior to 3.1.8 allows attackers with administrator rights to execute arbitrary SQL commands via unspecified vectors.

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

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

It affects 2 products.


Products: Wp-Olivecart Olivecart, Wp-Olivecart Olivecartpro.

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

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

## Is CVE-2016-4905 being exploited?

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

## Other vulnerabilities in WP-OliveCart

- [CVE-2016-4904](https://insights.sbomify.com/CVE-2016-4904/): Cross-site request forgery in WP-OliveCart (high 8.8)
- [CVE-2016-4903](https://insights.sbomify.com/CVE-2016-4903/): Cross-site scripting in WP-OliveCart (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4905 is a critical SQL injection vulnerability in WP-OliveCart, published on 22 May 2017. 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-4905 in the wild and no public exploit code.

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

## Sources

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

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