Description
SailingLab AppLock (aka com.alpha.applock) 4.3.8 for Android allows a local attacker to trigger arbitrary JavaScript execution via BrowserMainActivity, which accepts VIEW intents with javascript: URIs. This unsafe navigation path results in script execution and may allow UI spoofing or privilege escalation.
Published: 2026-05-26
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

SailingLab AppLock (com.alpha.applock) version 4.3.8 for Android includes a flaw in BrowserMainActivity that accepts VIEW intents containing javascript: URIs. When such an intent is processed, the embedded JavaScript is executed inside the application’s context, allowing a local attacker to run arbitrary code. This can lead to user interface spoofing or privilege escalation within the app, potentially compromising user data or enabling further malicious actions. The vulnerability is a direct result of unsafe navigation handling, enabling arbitrary code execution.

Affected Systems

The affected product is SailingLab AppLock (com.alpha.applock) version 4.3.8 for Android. No additional vendors or product versions are listed in the available data.

Risk and Exploitability

The EPSS score is not available and the vulnerability is not listed in CISA’s KEV catalog, indicating no publicly known exploits against it at this time. However, the nature of the flaw—local code execution—poses a significant risk if an attacker can inject a VIEW intent with a javascript: URI. Exploitation requires local access or the ability to influence intent transmission to the device, so the attack vector is local. The lack of a CVSS score means the severity cannot be quantified from available data, but the potential for complete compromise of the app’s execution environment warrants careful consideration.

Generated by OpenCVE AI on May 26, 2026 at 20:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update to the latest version of SailingLab AppLock that removes the vulnerable intent handling
  • Restrict or remove the BrowserMainActivity from processing VIEW intents that contain "javascript:" URIs by adjusting the app’s manifest intent filters
  • Configure the application or device to deny externally crafted intents that target the app’s main activity, or employ a security policy that limits intent exposure to trusted origins

Generated by OpenCVE AI on May 26, 2026 at 20:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 26 May 2026 20:45:00 +0000

Type Values Removed Values Added
Title Local Android AppLock Allows JavaScript Execution via VIEW Intents
Weaknesses CWE-94

Tue, 26 May 2026 19:45:00 +0000

Type Values Removed Values Added
Description SailingLab AppLock (aka com.alpha.applock) 4.3.8 for Android allows a local attacker to trigger arbitrary JavaScript execution via BrowserMainActivity, which accepts VIEW intents with javascript: URIs. This unsafe navigation path results in script execution and may allow UI spoofing or privilege escalation.
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-05-26T19:13:56.394Z

Reserved: 2025-12-24T00:00:00.000Z

Link: CVE-2025-68709

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-05-26T20:16:16.167

Modified: 2026-05-26T20:19:21.240

Link: CVE-2025-68709

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-26T20:30:15Z

Weaknesses