# CVE-2025-47872: EG4 Electronics EG4 Inverters Observable Discrepancy

> Attackers can enumerate valid serial numbers and registration status via timing or response discrepancies on the public registration endpoint.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/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-vp38-x48w-r4cx

## What is CVE-2025-47872?

CVE-2025-47872 is a medium-severity 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 public-facing product registration endpoint server responds 
differently depending on whether the S/N is valid and unregistered, 
valid but already registered, or does not exist in the database. 
Combined with the fact that serial numbers are sequentially assigned, 
this allows an attacker to gain information on the product registration 
status of different S/Ns.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2025-47872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47872 is a medium-severity 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-47872 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-47872/ (Markdown: https://insights.sbomify.com/CVE-2025-47872/index.md)
```

## Sources

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

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