CVE-2025-1940: Android Intent confirmation prompt tapjacking using Select options
A select option could partially obscure the confirmation prompt shown before launching external apps. This could be used to trick a user in to launching an external app unexpectedly.
*This issue only affects Android versions of Firefox.*. This vulnerability was fixed in Firefox 136.
Security readout for executives and security teams
Plain-English summary
CVE-2025-1940 is an Android-only Firefox flaw where a page element could partially cover the warning shown before opening an external app. A user could be misled into launching another app unexpectedly. Mozilla states this was fixed in Firefox 136.
Executive priority
Treat this as a high-priority mobile browser update issue, not an emergency breach indicator. The business risk is user deception leading to unintended app launches, with high potential confidentiality impact in Mozilla's CVSS scoring.
Technical view
The issue is a tapjacking-style UI problem tied to select options obscuring Android Firefox's external-app intent confirmation prompt. CVSS 3.1 is 7.1: network-reachable, low attack complexity, no privileges required, but user interaction is required. The listed weakness is CWE-1021.
Likely exposure
Exposure is most relevant to Android devices running Firefox versions before the fixed Firefox 136 release. Desktop Firefox is not indicated as affected in the source bundle. Organizations with unmanaged Android browsers or delayed mobile patching are more likely exposed.
Exploitation context
The bundle does not cite active exploitation, and CISA KEV status is false. Practical abuse would require convincing a user to interact with content that causes the misleading external-app launch prompt. No exploit availability is established by the supplied sources.
Researcher notes
Evidence supports an Android Firefox tapjacking issue fixed in Firefox 136. The source bundle does not provide confirmed exploitation, exploit maturity, or broader product impact. Avoid assuming non-Android Firefox exposure without vendor confirmation.
Mitigation direction
Update Android Firefox to version 136 or later.
Prioritize managed Android fleets and high-risk mobile users.
Verify mobile device management policies enforce browser updates.
Review Mozilla advisory and Bugzilla for any later vendor guidance.
Validation and detection
Inventory Android devices running Firefox and record installed versions.
Confirm Android Firefox is version 136 or later.
Check whether unmanaged Android devices can bypass update controls.
Monitor helpdesk or telemetry for unexpected external-app launches.
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 · low confidence lookup
CWE-1021: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1021 · source CWE mapping
Improper Restriction of Rendered UI Layers or Frames
Improper Restriction of Rendered UI Layers or Frames represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.