FirefoxWeb browser · Mozilla

CVE-2021-29953

MEDIUM · 6.1 CVSS v3.1 Published 2021-06-24
Fix available
A fix is available. Upgrade to 88.0.1 / 88.1.3 or later.
See remediation →
68/100
Remediation priority · Elevated
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 malicious webpage could have forced a Firefox for Android user into executing attacker-controlled JavaScript in the context of another domain, resulting in a Universal Cross-Site Scripting vulnerability. *Note: This issue only affected Firefox for Android. Other operating systems are unaffected. Further details are being temporarily withheld to allow users an opportunity to update.*. This vulnerability affects Firefox < 88.0.1 and Firefox for Android < 88.1.3.

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 · moderate confidence

A Universal Cross-Site Scripting (UXSS) vulnerability in Firefox for Android allows a malicious webpage to force execution of attacker-controlled JavaScript in the context of a different domain. This cross-origin JavaScript execution occurs due to improper handling of browser context or origin isolation in the Firefox for Android browser engine.

MitigationUpdate Firefox for Android to version 88.1.3 or later to patch this UXSS vulnerability. Organizations should ensure mobile devices are running the patched browser version.

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:< 88.0.1< 88.1.3

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Confirm Firefox for Android is installed
    Open the device settings, go to Apps, and look for Mozilla Firefox in the installed applications list, or check the app icon on the home screen
    Affected if Firefox for Android is not present on the device
  2. Find the installed Firefox for Android version number
    Open Firefox for Android, tap the three-dot menu, go to Settings, then scroll down and tap 'About Firefox' - the version number will be displayed
    Affected if Cannot locate version information or the app is not Firefox for Android
  3. Compare installed version against affected range
    Note the version number from the About screen and compare it to the affected versions: any version below 88.1.3 is considered vulnerable
    Affected if Installed version is less than 88.1.3 (for example, 88.0, 87.x, or earlier)
  4. Verify the update status
    In Firefox for Android, tap the three-dot menu and look for an 'Update' option in Settings, or visit the Google Play Store and check for Firefox updates
    Affected if A newer version is available or the browser has not been updated to 88.1.3 or later

The user is affected if Firefox for Android is installed with a version number lower than 88.1.3, as this UXSS vulnerability allows cross-origin JavaScript execution through improper browser context handling.

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.

From vendor data
Upgrade available Upgrade to 88.0.1 / 88.1.3 or later
Fixed in 88.0.188.1.3
Interim mitigation

Update Firefox for Android to version 88.1.3 or later to patch this UXSS vulnerability. Organizations should ensure mobile devices are running the patched browser version.

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29953 — 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-2021-29953 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