LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68709: SailingLab AppLock (aka com.alpha.applock) 4.3.8 for Android allows a local attacker to trigger arbitrary J...

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.

MediumCVSS 5.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-68709 affects SailingLab AppLock for Android, version 4.3.8. A local attacker may cause the app to run JavaScript through an unsafe browser intent path. The business risk is mobile user trust: UI spoofing or limited privilege-related impact may be possible if a user is induced to interact.

Executive priority

Prioritize as moderate for organizations that allow this Android app on managed or sensitive devices. The issue is not documented as actively exploited, but it affects a security-themed app and could undermine user trust through spoofing or limited integrity impact.

Technical view

BrowserMainActivity accepts Android VIEW intents containing javascript: URIs, creating an unsafe navigation path that can execute arbitrary JavaScript. The CVSS 3.1 score is 5.2 with low complexity, required user interaction, changed scope, and low confidentiality and integrity impact. The listed weakness is CWE-79.

Likely exposure

Exposure appears limited to Android devices with SailingLab AppLock, package com.alpha.applock, specifically version 4.3.8 per the CVE description. The source bundle does not provide CPEs, enterprise deployment prevalence, or a vendor-fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability requires a local or app-adjacent trigger path and user interaction. Treat exploit status as unconfirmed rather than active.

Researcher notes

Evidence is narrow: the CVE names AppLock 4.3.8 and the unsafe BrowserMainActivity javascript: URI handling, but affected metadata is listed as n/a and no patch is identified. Avoid broad product assumptions until vendor or repository guidance clarifies affected versions and fixes.

Mitigation direction

  • Inventory managed Android devices for com.alpha.applock version 4.3.8.
  • Check Google Play and vendor guidance for a fixed release or advisory.
  • Update the app when a vendor-fixed version is confirmed.
  • Remove or restrict the app on managed devices if risk is unacceptable.
  • Limit sideloading and untrusted app installation on Android fleets.

Validation and detection

  • Confirm installed package name and version through MDM or device inventory.
  • Check whether AppLock 4.3.8 is present on high-risk user devices.
  • Review vendor, Play Store, and CVE records for updated remediation guidance.
  • Confirm the CVE remains absent from CISA KEV before claiming no known exploitation.
  • Assess mobile security logs for suspicious inter-app launch activity.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-68709 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.2CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.12.7CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.2Medium
CVSS 3.1 vector shape for CVE-2025-68709Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.