CVE-2025-68712
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpSoft AppLock (com.sp.protector.free) 7.9.40 for Android allows a local attacker with physical access to bypass fingerprint or PIN authentication. Although the app integrates Android's biometric mechanisms, the lock is implemented with a custom overlay that fails to consistently enforce authentication. By navigating cascading interface flows - insecure navigation through exposed routes facilitates app control evasion {I.N.T.E.R.F.A.C.E] via advertisement or browser intents - an attacker can exit the lock interface without re-authentication and access protected apps (e.g., Chrome). This results in information disclosure and privilege escalation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSpSoft AppLock 7.9.40 for Android fails to consistently enforce biometric/PIN authentication due to a custom overlay with insecure navigation. A local attacker with physical access can exploit exposed routes through advertisement or browser intents to bypass the lock screen and access protected applications like Chrome, resulting in information disclosure and privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if SpSoft AppLock is installedCheck device applications for SpSoft AppLock or com.spsoft.applock in the app package list. Use 'adb shell pm list packages' or check device settings under Apps.Affected if SpSoft AppLock version 7.9.40 is installed on the device.
-
Confirm the installed versionRetrieve the exact version number from the app info page in Android Settings under Apps > AppLock > App info, or use 'adb shell dumpsys package com.spsoft.applock | grep versionName'.Affected if The installed version matches 7.9.40 exactly.
-
Verify biometric or PIN lock is enabledOpen AppLock settings and check if biometric authentication or PIN lock is turned ON under the authentication settings.Affected if Biometric or PIN lock is enabled for the application.
-
Check if browser apps are protectedIn AppLock, navigate to the protected apps list and verify whether Chrome or other browsers are included in the protected applications.Affected if Chrome or any browser application is listed as a protected app under AppLock.
-
Confirm custom lock overlay is activeObserve the lock screen behavior when launching a protected app - verify that AppLock displays its custom overlay prompt before allowing access.Affected if The custom AppLock overlay appears when opening protected applications.
A user is affected if SpSoft AppLock version 7.9.40 is installed with biometric or PIN protection enabled and browser apps are protected by the custom overlay, allowing insecure intent navigation to bypass the lock screen.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataVendor should patch the custom overlay to consistently enforce authentication across all interface flows and remove or properly guard exposed intent routes that allow unauthorized exit from the lock screen.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-68712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data