dbcve.org
SafariWeb browser · Apple

CVE-2025-24150

HIGH · 8.8 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 15.3 / 18.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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
A privacy issue was addressed with improved handling of files. This issue is fixed in Safari 18.3, iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3. Copying a URL from Web Inspector may lead to command injection.

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

A command injection vulnerability exists in Web Inspector where copying a URL can lead to arbitrary command execution. The issue stems from improper handling of file URLs during clipboard operations, allowing injected commands to be executed when the copied URL is used.

MitigationUpdate to Safari 18.3, iOS 18.3/iPadOS 18.3, or macOS Sequoia 15.3 to receive the fix for improved file URL handling in Web Inspector.

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
SafariWeb browser
Affected:< 18.3
IpadosOperating system
Affected:< 18.3
Iphone OsOperating system
Affected:< 18.3
macOSOperating system
Affected:< 15.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Safari version on macOS
    Open Safari, go to Safari menu > About Safari. Compare the version number to 18.3.
    Affected if The installed Safari version is earlier than 18.3 on macOS.
  2. Check iOS version on iPhone
    Go to Settings > General > About. Look at the Software Version. Compare to 18.3.
    Affected if The iOS version is earlier than 18.3.
  3. Check iPadOS version on iPad
    Go to Settings > General > About. Look at the Software Version. Compare to 18.3.
    Affected if The iPadOS version is earlier than 18.3.
  4. Check macOS version
    Go to Apple menu > About This Mac. The macOS version number appears below the name. Compare to 15.3.
    Affected if The macOS version is earlier than 15.3 (Sequoia 15.3 or later).
  5. Verify if Web Inspector is enabled in Safari
    In Safari on macOS, go to Safari > Settings > Advanced and check if 'Show Develop menu in menu bar' is enabled. On iOS/iPadOS, Web Inspector requires the Develop menu which is enabled via Safari settings on the connected device.
    Affected if Web Inspector is enabled and you copy URLs from the inspector's console or network tabs.

You are affected if your Safari/iOS/iPadOS version is earlier than 18.3 or your macOS is earlier than 15.3, AND you use Web Inspector to copy URLs.

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 15.3 / 18.3 or later
Fixed in 15.318.3
Interim mitigation

Update to Safari 18.3, iOS 18.3/iPadOS 18.3, or macOS Sequoia 15.3 to receive the fix for improved file URL handling in Web Inspector.

Recommended fix High confidence

iOS 18.3, iPadOS 18.3, Safari 18.3, macOS Sequoia 15.3

  1. Open Settings on iOS/iPadOS, or System Settings on macOS
  2. Navigate to General > Software Update (or System Preferences > Software Update on older macOS)
  3. Check for and install the available update
  4. Ensure the device updates to iOS 18.3, iPadOS 18.3, or macOS Sequoia 15.3 respectively
  5. For Safari on macOS, update to Safari 18.3 through the macOS software update
  6. After updating, verify the version in Settings > General > About (iOS/iPadOS) or Safari > About Safari (macOS)
Caveat Standard Apple OS update considerations apply - ensure backups exist before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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