CVE-2025-68712: com.sp.protector.free · Improper Authentication
Affects com.sp.protector.freeSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 May 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubactuator/com.sp.protector.freepkg:github/actuator/com.sp.protector.freeOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, users should limit physical access to their devices and consider using alternative app locking solutions with verified security. No official remediation or temporary fix is documented at this time.
Description
SpSoft AppLock version 7.9.40 for Android contains a vulnerability that allows a local attacker with physical access to bypass fingerprint or PIN authentication. The app uses a custom overlay for locking, which does not consistently enforce authentication due to insecure navigation through exposed routes triggered by advertisement or browser intents. This flaw enables an attacker to exit the lock interface without re-authenticating and access protected applications such as Chrome, leading to information disclosure and privilege escalation.