FirefoxWeb browser · Mozilla
CVE-2025-54144
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 · uneditedThe URL scheme used by Firefox to facilitate searching of text queries could incorrectly allow attackers to open arbitrary website URLs or internal pages if a user was tricked into clicking a link. This vulnerability was fixed in Firefox for iOS 141.
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 confidenceFirefox for iOS contained a URL scheme handler flaw in its text search functionality that failed to properly validate incoming URLs. Attackers could craft malicious links that, when clicked, would cause Firefox to open arbitrary external websites or internal application pages beyond the intended search behavior.
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
< 141.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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Confirm you are using Firefox for iOSCheck if the installed browser is Mozilla Firefox for iOS (mobile app), not Firefox for desktop or other Firefox variants. On iOS, go to Settings > Firefox to verify the app.Affected if The app is Firefox for iOS on any version below 141.0
-
Identify the installed Firefox for iOS versionOpen the Firefox for iOS app, tap the menu (three lines), go to Settings, then scroll to the bottom where the version number is displayed. Alternatively, check in the iOS App Store or your device's app information.Affected if The displayed version number is less than 141.0 (for example, 140.x, 139.x, etc.)
-
Verify the text search URL scheme is accessibleThe vulnerability exists in how Firefox for iOS handles URLs with the search scheme (such as firefox://search?term=). Test if this scheme is processed by the app, which can be triggered via custom URL handlers or deep links.Affected if Firefox for iOS processes incoming URLs through its search URL scheme handler and the version is below 141.0
You are affected if Firefox for iOS is installed at a version lower than 141.0 and the app processes text search URL scheme requests.
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 · scoped141.0
Update Firefox for iOS to version 141 or later to obtain the patched URL scheme handler. Users should avoid clicking untrusted links that trigger the Firefox search URL scheme.
Firefox for iOS 141.0
- Open the App Store on your iOS device
- Search for "Firefox" or "Mozilla Firefox"
- Tap the update button if Firefox is listed, or download/install Firefox for iOS 141.0 or later
- Restart the application if needed after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54144 — 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-54144 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