FirefoxWeb browser · Mozilla

CVE-2025-1940

HIGH · 7.1 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 136.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A UI obscuring vulnerability in Firefox for Android allows a select HTML element to partially cover the external app launch confirmation dialog. By manipulating the select option positioning, attackers can hide parts of the confirmation prompt, tricking users into launching external applications they did not intend to open.

MitigationUpdate Firefox for Android to version 136 or later. Users should verify the full confirmation prompt is visible before accepting external app launches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FirefoxWeb browser
Affected:< 136.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Firefox product
    Check if Mozilla Firefox for Android is installed on the device. This vulnerability affects only the Android version, not desktop Firefox.
    Affected if The product is Firefox for Android specifically
  2. Check Firefox for Android version number
    Navigate to Firefox for Android Settings > About Firefox. Locate the version number displayed.
    Affected if The version number is below 136.0 (for example, 135.3, 135.0, or earlier)
  3. Verify external app launch functionality is accessible
    Confirm that web pages can trigger external app launch prompts via intent URLs or the select element behavior in Firefox for Android.
    Affected if External app launch dialogs can be triggered through web content in the browser

A user is affected if Firefox for Android is installed with a version lower than 136.0 and web pages can trigger external app launch confirmation dialogs that could be obscured by select elements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 136.0 or later
Fixed in 136.0
Interim mitigation

Update Firefox for Android to version 136 or later. Users should verify the full confirmation prompt is visible before accepting external app launches.

Recommended fix High confidence

Firefox 136.0 (Android)

  1. Open the Google Play Store on your Android device
  2. Search for "Firefox" or locate it in your installed apps
  3. Tap "Update" to update Firefox to version 136.0 or later
  4. After the update completes, verify the version by going to Firefox > Settings > About Firefox - it should show version 136.0 or higher
  5. Restart Firefox to ensure the update is fully applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1940 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1940 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data