Cross-Site Scripting (XSS) in SailingLab AppLock (CVE-2025-68709)
Summary
Cross-site scripting in SailingLab AppLock (CVE-2025-68709). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-68709 has been found in SailingLab AppLock.
Risk of unauthorized operations or information disclosure. CVSS score: 5.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SailingLab AppLock CVE-2025-68709" on the vendor's site.
CVE-2025-68709 (SailingLab AppLock) — CWE-79 / CVSS v3 5.2
Attack vector: adjacent-network / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in SailingLab AppLock.
Check the vendor advisory for the affected versions of SailingLab AppLock.
Severity: Medium (CVSS 5.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで SailingLab AppLock を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web nvd.nist.gov
- web github.com