# CVE-2025-4534: SunGrow Logger1000 weak password

> Weak password requirements in SunGrow Logger1000 allow remote attackers to potentially compromise accounts despite high attack complexity.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 11 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-w886-q54p-h4w2

## What is CVE-2025-4534?

CVE-2025-4534 is a medium-severity vulnerability in SunGrow Logger1000, published on 11 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, has been found in SunGrow Logger1000 01_A. This issue affects some unknown processing. The manipulation leads to weak password requirements. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-521 (Weak Password Requirements)

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


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

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

## Is CVE-2025-4534 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4534 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4534 is a medium-severity vulnerability in SunGrow Logger1000, published on 11 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4534 exists.

Affected product: SunGrow Logger1000. 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-4534/ (Markdown: https://insights.sbomify.com/CVE-2025-4534/index.md)
```

## Sources

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

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