dbcve.org
FirefoxWeb browser · Mozilla

CVE-2025-14744

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 144.0 or later.
See remediation →
72/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
Unicode RTLO characters could allow malicious websites to spoof filenames in the downloads UI for Firefox for iOS, potentially tricking users into saving files of an unexpected file type. This vulnerability was fixed in Firefox for iOS 144.0.

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

Firefox for iOS failed to sanitize or neutralize Unicode RTLO (Right-to-Left Override, U+202E) characters in filenames displayed in the downloads UI. Attackers could craft malicious file names where RTLO characters reverse the display order, causing files like 'malware.exe' to appear as 'malware.txt', tricking users into downloading and executing unintended file types.

MitigationUpdate Firefox for iOS to version 144.0 or later. Users should verify downloaded files by checking actual file extensions in the device file system rather than relying solely on the download UI display.

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:< 144.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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. Check Firefox for iOS version
    Open the App Store app, search for Mozilla Firefox, and view the version number. Alternatively, open Firefox for iOS, tap the menu (three lines), go to Settings, and scroll to the bottom to see the version number.
    Affected if The installed version is lower than 144.0 (for example, 143.x or earlier).
  2. Confirm use of downloads UI
    Open Firefox for iOS and tap the menu icon, then tap Downloads (or access the downloads list through Settings > Downloads). Review whether you have any downloaded files listed in this UI.
    Affected if You have downloaded files displayed in the Firefox downloads UI, as this is where the RTLO character rendering vulnerability occurs.
  3. Inspect downloaded file names for RTLO characters
    For any files listed in the Firefox downloads UI, manually check if the displayed filename contains unusual characters or appears to have reversed text order. RTLO characters (U+202E) are invisible but cause text to display in reverse direction.
    Affected if A downloaded file displays a filename that appears to have reversed text order or contains suspicious character sequences that could hide the true file extension.

You are affected if Firefox for iOS version is below 144.0 AND you use the downloads UI to view file names, as the unsanitized RTLO characters in the UI can misrepresent true file extensions.

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 144.0 or later
Fixed in 144.0
Interim mitigation

Update Firefox for iOS to version 144.0 or later. Users should verify downloaded files by checking actual file extensions in the device file system rather than relying solely on the download UI display.

Recommended fix High confidence

Firefox for iOS 144.0

  1. 1. Open the App Store on your iOS device
  2. 2. Tap on your profile icon in the top right corner
  3. 3. Scroll down to see available updates
  4. 4. Locate Firefox in the list of apps with pending updates
  5. 5. Tap 'Update' next to Firefox to update to version 144.0 or later
  6. 6. Alternatively, search for 'Firefox' in the App Store and tap 'Update' if an update is available

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
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-14744 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