CVE-2025-63823: My Safetipin Android Application · Use of Hard-coded Credentials
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
AI-suggested
Until an official fix is released, users and administrators should consider restricting access to the affected version and monitor for updates from the vendor. Avoid using version 5.2.1 in production environments where possible.
Description
My Safetipin Android Application version 5.2.1 contains hardcoded credentials in its authentication module. This vulnerability allows remote attackers to bypass authentication by exploiting predictable OTP values, leading to unauthorized access to user accounts. The issue is classified as critical with a CVSS score of 9.8. No official patch or remediation guidance is currently available from the vendor.