dbcve.org
FirefoxWeb browser · Mozilla

CVE-2018-5110

MEDIUM · 5.3 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to after 57.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
If cursor visibility is toggled by script using from 'none' to an image and back through script, the cursor will be rendered temporarily invisible within Firefox. Note: This vulnerability only affects OS X. Other operating systems are not affected. This vulnerability affects Firefox < 58.

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

In Firefox versions prior to 58 on macOS, JavaScript can manipulate the CSS cursor property from 'none' to an image and back, causing the system cursor to become temporarily invisible. This UI inconsistency could enable social engineering or user confusion attacks where malicious content mimics trusted system UI elements.

MitigationUpgrade Firefox to version 58 or later on all macOS systems. For enterprises, deploy the updated browser version via patch management. Users should also be warned about potential cursor spoofing when visiting untrusted websites.

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:<= 57.0.4

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 is installed on macOS
    Check for the Firefox application in /Applications/Firefox.app or run 'ls /Applications | grep -i firefox' in Terminal
    Affected if Firefox is found in the Applications folder on a macOS system
  2. Determine the installed Firefox version
    Click Firefox menu > About Firefox, or run '/Applications/Firefox.app/Contents/MacOS/firefox --version' in Terminal, or check Info.plist for CFBundleShortVersionString
    Affected if The displayed version number is 57.0.4 or lower
  3. Confirm the operating system is macOS
    Run 'uname -s' in Terminal (should return Darwin) and 'sw_vers' to verify macOS, or check System Preferences > About
    Affected if The system is running macOS (any version)
  4. Verify the vulnerability condition
    Compare the installed Firefox version against the affected range: versions 57.0.4 and below on macOS are vulnerable
    Affected if Firefox version is less than or equal to 57.0.4 AND the operating system is macOS

A user is affected if they are running Firefox version 57.0.4 or lower on any macOS system, as the cursor property manipulation flaw exists in those versions.

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 a release after 57.0.4
Interim mitigation

Upgrade Firefox to version 58 or later on all macOS systems. For enterprises, deploy the updated browser version via patch management. Users should also be warned about potential cursor spoofing when visiting untrusted websites.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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