# CVE-2025-57433: Information disclosure in n/a

> An authenticated attacker can retrieve hashed passwords for admin, manager, and guest accounts via a crafted POST request, potentially leading to administrative access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 23 Sep 2025
- **Also known as:** GHSA-vfh3-px5r-4mqf

## What is CVE-2025-57433?

CVE-2025-57433 is a medium-severity vulnerability in n/a, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The 2wcom IP-4c 2.15.5 device's web interface includes an information disclosure vulnerability. By sending a crafted POST request to a specific endpoint (/cwi/ajax_request/get_data.php), an authenticated attacker (even with a low-privileged account like guest) can retrieve the hashed passwords for the admin, manager, and guest accounts. This significantly weakens the system's security posture, as these hashes could be cracked offline, granting attackers administrative access to the device.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: 2wcom Ip-4c Firmware.

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

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

## Is CVE-2025-57433 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-57438](https://insights.sbomify.com/CVE-2025-57438/): Missing authorization in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57433 is a medium-severity vulnerability in n/a, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57433 exists.

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

## Sources

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

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