# CVE-2020-37154: eLection 2.0 - 'id' SQL Injection


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-cgfw-66j9-q2xp

## What is CVE-2020-37154?

CVE-2020-37154 is a high-severity vulnerability in Tripath Project eLection, published on 6 Feb 2026. 

### Official description

eLection 2.0 contains an authenticated SQL injection vulnerability in the candidate management endpoint that allows attackers to manipulate database queries through the 'id' parameter. Attackers can leverage SQLMap to exploit the vulnerability, potentially gaining remote code execution by uploading backdoor files to the web application directory.

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

## Which versions are affected by CVE-2020-37154?


## How do I fix CVE-2020-37154?

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

## Is CVE-2020-37154 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37154 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37154 and fix it if it is affected.

What it is: CVE-2020-37154 is a high-severity vulnerability in Tripath Project eLection, published on 6 Feb 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37154 exists.

Affected product: Tripath Project eLection. 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-2020-37154/ (Markdown: https://insights.sbomify.com/CVE-2020-37154/index.md)
```

## Sources

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

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