# CVE-2023-7129: code-projects Voting System Voters Login sql injection

> Attackers can exploit SQL injection in the Voting System login to access or modify voter data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-h7fw-h5jr-wr5j

## What is CVE-2023-7129?

CVE-2023-7129 is a medium-severity SQL injection vulnerability in code-projects Voting System, published on 28 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in code-projects Voting System 1.0. Affected is an unknown function of the component Voters Login. The manipulation of the argument voter leads to sql injection. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-249132.

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

## Which versions are affected by CVE-2023-7129?

It affects 1 product.


Products: Code-Projects Voting System.

## How do I fix CVE-2023-7129?

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

## Is CVE-2023-7129 being exploited?

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

## Other vulnerabilities in code-projects Voting System

- [CVE-2023-7128](https://insights.sbomify.com/CVE-2023-7128/): code-projects Voting System Admin Login sql injection (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7129 and fix it if it is affected.

What it is: CVE-2023-7129 is a medium-severity SQL injection vulnerability in code-projects Voting System, published on 28 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7129 in the wild and no public exploit code.

Affected product: code-projects Voting System. 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-2023-7129/ (Markdown: https://insights.sbomify.com/CVE-2023-7129/index.md)
```

## Sources

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

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