# CVE-2025-57438: Missing authorization in n/a

> A manager-level user can bypass access controls to reach sensitive admin-only endpoints by modifying requests, leading to privilege escalation.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-j9x6-jxc8-5wfq

## What is CVE-2025-57438?

CVE-2025-57438 is a medium-severity missing authorization vulnerability in n/a, published on 22 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The 2wcom IP-4c 2.15.5 device suffers from a Broken Access Control vulnerability. Certain sensitive endpoints are intended to be accessible only after the admin explicitly grants access to a manager-level account. However, a manager-level user can bypass these controls by intercepting and modifying requests.

Weakness: CWE-285 (Improper Authorization), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: 2wcom Ip-4c Firmware.

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

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

## Is CVE-2025-57438 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-57433](https://insights.sbomify.com/CVE-2025-57433/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57438 is a medium-severity missing authorization vulnerability in n/a, published on 22 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57438 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-57438/ (Markdown: https://insights.sbomify.com/CVE-2025-57438/index.md)
```

## Sources

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

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