Skip to main content
VulnerabilityPublished

CVE-2025-27388: OPPO HEALTH APP · Improper Input Validation

Affects OPPO HEALTH APPSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
OPPO OPPO HEALTH APPAffected
  • <=4.23.4
Fixed in–

AI-suggested

1. Immediate mitigation involves updating the OPPO Health App to a patched version once available. 2. Until a patch is released, organizations should restrict or monitor the use of OPPO Health App on corporate or sensitive devices, especially those running vulnerable versions (4.23.4 and below). 3. Implement network-level controls to block access to suspicious or untrusted external URLs that could be loaded by the app's WebView. 4. Educate users about the risks of clicking unknown links or opening untrusted URLs within the app to reduce the likelihood of exploitation via social engineering. 5. Employ mobile device management (MDM) solutions to enforce app version compliance and restrict installation of vulnerable app versions. 6. Monitor for unusual authentication token usage or account activity that could indicate token theft. 7. Encourage multi-factor authentication (MFA) on accounts accessed via the app to mitigate the impact of stolen tokens. 8. Consider isolating or sandboxing the app environment to limit the impact of malicious JavaScript execution within WebView.

Description

Loading arbitrary external URLs through WebView components introduces malicious JS code that can steal arbitrary user tokens.

References

Community reviews

Loading reviews…