FirefoxWeb browser · Mozilla

CVE-2023-37455

MEDIUM · 5.4 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 115 or later.
See remediation →
61/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
The permission request prompt from the site in the background tab was overlaid on top of the site in the foreground tab. This vulnerability affects Firefox for iOS < 115.

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

This is a cross-tab UI confusion vulnerability in Firefox for iOS where permission request prompts (such as camera, microphone, or location access) from a background tab incorrectly overlay on top of the foreground tab. This can trick users into granting sensitive permissions to a site they did not intentionally interact with, as the prompt appears to come from the visible foreground site rather than the actual requesting background site.

MitigationUpgrade Firefox for iOS to version 115 or later to receive the patch that properly handles permission prompt layering and prevents background tab requests from overlaying foreground tab content.

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:< 115

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

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

  1. Verify Firefox for iOS is installed
    Navigate to the iOS Settings app, scroll down to find the list of installed applications, and confirm that Mozilla Firefox appears in the list.
    Affected if Firefox for iOS is present on the device
  2. Locate the Firefox for iOS version number
    Open the iOS Settings app, tap on Mozilla Firefox in the applications list, then locate the 'Version' field displayed under the app name.
    Affected if Unable to locate version information for Firefox for iOS
  3. Compare installed version against affected range
    Read the version number shown (for example, 114.0, 114.1, etc.) and compare it numerically to version 115.0. Any version less than 115.0 falls within the affected range.
    Affected if The installed version is a three-digit number less than 115 (such as 114.x, 113.x, or any earlier version)
  4. Confirm iOS version compatibility (optional context)
    This check is informational only: verify the device is running a supported iOS version that can run Firefox 115 or later, as some older devices may be limited to older Firefox versions.
    Affected if Device iOS version restricts upgrade path to Firefox versions below 115

A user is affected if Mozilla Firefox for iOS is installed with a version number lower than 115.

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

Upgrade Firefox for iOS to version 115 or later to receive the patch that properly handles permission prompt layering and prevents background tab requests from overlaying foreground tab content.

Recommended fix High confidence

Firefox for iOS 115 or later

  1. Open the App Store on your iOS device
  2. Search for Firefox or Firefox for iOS
  3. Tap the Update button next to Firefox to update to version 115 or later
  4. Alternatively, enable automatic updates in App Store settings to receive future security updates

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

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