CVE-2025-47697

CVE-2025-47697 is a high-severity vulnerability in Uchida Wivia 5 Firmware with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-602.

Key facts

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.

Frequently asked questions

What is CVE-2025-47697?
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.
How severe is CVE-2025-47697?
CVE-2025-47697 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2025-47697 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-47697?
CVE-2025-47697 affects Uchida Wivia 5 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-47697?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-47697 have an EU (EUVD) identifier?
Yes. CVE-2025-47697 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16464.
When was CVE-2025-47697 published?
CVE-2025-47697 was published on 2025-05-30 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Uchida Wivia 5 Firmware

All CVEs affecting Uchida Wivia 5 Firmware →

Other CWE-602 vulnerabilities

Browse all CWE-602 vulnerabilities →