# CVE-2012-6427: Carlo Gavazzi EOS Box SQL Injection

> Unauthenticated attackers can exploit SQL injection in Carlo Gavazzi EOS Box to leak sensitive device information, compromising confidentiality.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2012
- **Updated:** 1 Jul 2025
- **Also known as:** GHSA-7qc4-45cg-h6f3

## What is CVE-2012-6427?

CVE-2012-6427 is a high-severity SQL injection vulnerability in Carlo Gavazzi Automation EOS-Box, published on 23 Dec 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Carlo Gavazzi 
EOS-Box

does not check the validity of the data before executing queries. By accessing the SQL table of certain pages that do not require authentication, attackers can leak information from the device. This could allow the attacker to compromise confidentiality.

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

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

It affects 2 products.


Products: Carlosgavazzi Eos-Box Photovoltaic Monitoring System, Carlosgavazzi Eos-Box Photovoltaic Monitoring System Firmware.

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

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

## Is CVE-2012-6427 being exploited?

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

## Other vulnerabilities in Carlo Gavazzi Automation EOS-Box

- [CVE-2012-6428](https://insights.sbomify.com/CVE-2012-6428/): Carlo Gavazzi EOS Box Hard-Coded Credentials (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6427 is a high-severity SQL injection vulnerability in Carlo Gavazzi Automation EOS-Box, published on 23 Dec 2012. 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-2012-6427 in the wild and no public exploit code.

Affected product: Carlo Gavazzi Automation EOS-Box. 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-6427/ (Markdown: https://insights.sbomify.com/CVE-2012-6427/index.md)
```

## Sources

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

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