What is the CVSS score of CVE-2025-63823?

CVE-2025-63823 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of My Safetipin are affected by CVE-2025-63823?

My Safetipin Android application version 5.2.1 contains an unauthenticated authentication bypass vulnerability enabling account takeover through hardcoded credentials and predictable OTP generation.

How to fix or mitigate CVE-2025-63823?

Within 24 hours: Identify all instances of My Safetipin version 5.2.1 or earlier running on managed and personal devices, notify all affected users of the account takeover risk, and disable push installations and updates to this application if managed centrally. Within 7 days: Contact My Safetipin vendor to confirm security patch timeline and request interim mitigation guidance; implement network-level access controls or app-level restrictions to limit exposure if the application remains in active use. Within 30 days: Deploy vendor-released patch to My Safetipin immediately upon availability, conduct forensic audit of all user accounts for evidence of unauthorized access or data modification, and enforce password resets for all affected accounts as a precautionary measure.

My Safetipin CVE-2025-63823

EUVD-2025-210622 CRITICAL

Use of Hard-coded Credentials (CWE-798)

2026-08-05 mitre

GHSA-hcqf-2mp3-h5vf

Authentication Bypass Google N A

9.8

CVSS 3.1 · Vendor: mitre

Severity by source

Vendor (mitre) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

9.1 CRITICAL

Predictable OTP enables unauthenticated remote account takeover (PR:N, AC:L, AV:N) with full data read/modify (C:H/I:H); no described service-disruption vector, so A:N rather than the input's A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 06, 2026 - 15:56 vuln.today

CVSS changed

Aug 06, 2026 - 15:22 NVD

9.8 (None) 9.8 (CRITICAL)

CVE Published

Aug 05, 2026 - 00:00 cve.org

CRITICAL 9.8

CVE Published

Aug 05, 2026 - 00:00 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

My Safetipin Android Application 5.2.1 contains Hardcoded credentials in the authentication module, which allows remote attackers to bypass authentication and gain unauthorized access to user accounts via predictable OTP values.

AnalysisAI

Authentication bypass in the My Safetipin Android application version 5.2.1 stems from hardcoded credentials in the authentication module that produce predictable OTP values, letting remote attackers log in as arbitrary users and take over accounts without legitimate credentials. Any personal-safety data stored in a victim's account - location history, safety pins, and profile details - becomes exposed and modifiable. No public exploit has been identified at time of analysis, and the EPSS score of 0.27% (18th percentile) reflects low observed exploitation activity despite the maximal CVSS rating.

Technical ContextAI

The affected component is a consumer Android mobile app (com.safetipin.mysafetipin) distributed via Google Play, designed for personal/women's safety with features such as location safety scoring and pinning. The root cause is CWE-798 (Use of Hard-coded Credentials): a secret or seed embedded in the client authentication module makes the one-time-password generation deterministic. Because the OTP that should serve as a possession-based second factor is derived from static, predictable values rather than a per-user random secret, the OTP verification step becomes forgeable, collapsing the authentication guarantee. CPE data is uninformative here (cpe:2.3:a:n/a:n/a:*), so the affected identifier rests on the vendor package name and the stated version 5.2.1.

RemediationAI

No vendor-released patch identified at time of analysis; no fixed version is stated in the available data, so do not assume a specific upgrade target exists yet. Users should update My Safetipin to the latest Google Play build once Safetipin ships a release that replaces the hardcoded OTP seed with a server-side, per-user random secret, and should treat any accounts on 5.2.1 as potentially compromised. As compensating controls until a fix is confirmed: monitor the third-party advisory (https://github.com/Leoccc98/cve-reports/blob/main/advisories/CVE-2025-63823/README.md) and NVD (https://nvd.nist.gov/vuln/detail/CVE-2025-63823) for a patched version; the vendor should move OTP generation and verification entirely to the backend, invalidate existing sessions/tokens, and force credential re-enrollment. End users concerned about exposure can avoid storing sensitive location data in the app and consider uninstalling until a fixed version is published; the trade-off is loss of the app's safety functionality during that period.