# CVE-2012-10006: ale7714 sigeprosi sql injection

> An attacker can perform SQL injection in the sigeprosi web application to read or modify data, requiring a patch for remediation.

- **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:** 18 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-37x9-rwfr-2hj5

## What is CVE-2012-10006?

CVE-2012-10006 is a medium-severity SQL injection vulnerability in ale7714 sigeprosi, published on 18 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in ale7714 sigeprosi. This affects an unknown part. The manipulation leads to sql injection. The identifier of the patch is 5291886f6c992316407c376145d331169c55f25b. It is recommended to apply a patch to fix this issue. The identifier VDB-218493 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2012-10006?

It affects 1 product.


Products: Sigeprosi Project Sigeprosi.

## How do I fix CVE-2012-10006?

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

## Is CVE-2012-10006 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-10006 and fix it if it is affected.

What it is: CVE-2012-10006 is a medium-severity SQL injection vulnerability in ale7714 sigeprosi, published on 18 Jan 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-2012-10006 in the wild and no public exploit code.

Affected product: ale7714 sigeprosi. 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-2012-10006/ (Markdown: https://insights.sbomify.com/CVE-2012-10006/index.md)
```

## Sources

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

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