Firefox FocusWeb browser · Mozilla
CVE-2025-55032
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 · uneditedFocus for iOS would not respect a Content-Disposition header of type Attachment and would incorrectly display the content inline, potentially allowing for XSS attacks. This vulnerability was fixed in Focus for iOS 142.
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 confidenceFocus for iOS failed to honor the HTTP Content-Disposition header when set to 'Attachment', rendering potentially malicious content inline within the app instead of triggering a download/save prompt. This bypass of the security mechanism could enable stored XSS attacks if an attacker controls content served with this header misconfiguration.
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
Firefox FocusWeb browser
< 142.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Firefox Focus for iOS is installedOpen the iOS App Library or home screen and locate the Firefox Focus app icon. If not visible, search for it using Spotlight (swipe down and type 'Firefox Focus').Affected if The app is installed on the device.
-
Identify the installed version of Firefox Focus for iOSOpen the App Store app, tap your profile icon in the top right, tap 'Purchased', then find and tap 'Firefox Focus' from the list. The version number will be displayed on the app page. Alternatively, go to Settings > scroll down to Firefox Focus and tap it to view version details.Affected if The version displayed is less than 142.0 (for example, 141.x or earlier).
A user is affected if Firefox Focus for iOS is installed and the installed version is below 142.0.
Generated from the published advisory. Verify against your own configuration.
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 · scoped142.0
Update Focus for iOS to version 142 or later. Until then, avoid opening untrusted links within the app.
Firefox Focus for iOS 142.0 or later
- Open the App Store on the iOS device
- Search for "Firefox Focus" in the App Store
- Tap the Update button next to Firefox Focus to update to version 142.0 or later
- Alternatively, go to Settings > App Store > Automatic Downloads and enable Automatic App Updates to ensure the app stays updated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox Focus
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55032 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55032 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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