# CVE-2025-47697: Auth bypass in wivia 5

> An unauthenticated attacker can bypass authentication and operate the wivia 5 device as a moderator due to client-side enforcement of server-side security.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/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:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-frx7-938w-4px3

## What is CVE-2025-47697?

CVE-2025-47697 is a medium-severity authentication bypass vulnerability in UCHIDA YOKO CO., LTD. wivia 5, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Client-side enforcement of server-side security issue exists in wivia 5 all versions. If exploited, an unauthenticated attacker may bypass authentication and operate the affected device as the moderator user.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

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

It affects 1 product.


Products: Uchida Wivia 5 Firmware.

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

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

## Is CVE-2025-47697 being exploited?

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

## Other vulnerabilities in UCHIDA YOKO CO., LTD. wivia 5

- [CVE-2025-41385](https://insights.sbomify.com/CVE-2025-41385/): Command injection in wivia 5 (high 7.1)
- [CVE-2025-41406](https://insights.sbomify.com/CVE-2025-41406/): Cross-site scripting in wivia 5 (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47697 is a medium-severity authentication bypass vulnerability in UCHIDA YOKO CO., LTD. wivia 5, published on 30 May 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-47697 in the wild and no public exploit code.

Affected product: UCHIDA YOKO CO., LTD. wivia 5. 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-47697/ (Markdown: https://insights.sbomify.com/CVE-2025-47697/index.md)
```

## Sources

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

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