# CVE-2017-2120: SQL injection in WBCE CMS

> Administrators can execute arbitrary SQL commands in WBCE CMS, potentially compromising database integrity and confidentiality.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-32rq-3rm7-fq3r

## What is CVE-2017-2120?

CVE-2017-2120 is a high-severity SQL injection vulnerability in WBCE CMS, published on 28 Apr 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SQL injection vulnerability in the WBCE CMS 1.1.10 and earlier allows attacker 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-2017-2120?

It affects 1 product.


Products: Wbce Wbce Cms.

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

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

## Is CVE-2017-2120 being exploited?

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

## Other vulnerabilities in WBCE CMS

- [CVE-2023-39796](https://insights.sbomify.com/CVE-2023-39796/): SQL injection in n/a (critical 9.8)
- [CVE-2022-46020](https://insights.sbomify.com/CVE-2022-46020/): File upload in n/a (critical 9.8)
- [CVE-2021-3817](https://insights.sbomify.com/CVE-2021-3817/): SQL Injection in wbce/wbce_cms (critical 9.8)
- [CVE-2025-65950](https://insights.sbomify.com/CVE-2025-65950/): WBCE CMS is Vulnerable to Time-Based Blind SQL Injection through groups[] Parameter (critical 9.4)
- [CVE-2025-67504](https://insights.sbomify.com/CVE-2025-67504/): WBCE CMS has Weak Random Number Generator in Password Generation Function (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2120 is a high-severity SQL injection vulnerability in WBCE CMS, published on 28 Apr 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2120 in the wild and no public exploit code.

Affected product: WBCE CMS. 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-2120/ (Markdown: https://insights.sbomify.com/CVE-2017-2120/index.md)
```

## Sources

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

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