# CVE-2025-46414: EG4 Electronics EG4 Inverters Improper Restriction of Excessive Authentication Attempts

> Attackers can brute-force PINs to gain unauthorized access to EG4 solar inverters if they know the device serial number.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-xh3j-m8p6-2hjh

## What is CVE-2025-46414?

CVE-2025-46414 is a critical authentication bypass vulnerability in EG4 12000XP, published on 8 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected product does not limit the number of attempts for inputting
 the correct PIN for a registered product, which may allow an attacker 
to gain unauthorized access using brute-force methods if they possess a 
valid device serial number. The API provides clear feedback when the 
correct PIN is entered. This vulnerability was patched in a server-side 
update on April 6, 2025.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2025-46414?


## How do I fix CVE-2025-46414?

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

## Is CVE-2025-46414 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46414 and fix it if it is affected.

What it is: CVE-2025-46414 is a critical authentication bypass vulnerability in EG4 12000XP, published on 8 Aug 2025. 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-2025-46414 in the wild and no public exploit code.

Affected product: EG4 12000XP. 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-2025-46414/ (Markdown: https://insights.sbomify.com/CVE-2025-46414/index.md)
```

## Sources

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

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