dbcve.org
macOSOperating system · Apple

CVE-2025-24207

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 13.7.5 / 14.7.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A permissions issue was addressed with additional restrictions. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An app may be able to enable iCloud storage features without user consent.

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

A permissions bypass vulnerability in macOS allowed malicious applications to enable iCloud storage features without user consent, potentially exfiltrating data to iCloud without the user's knowledge or authorization.

MitigationApply the appropriate macOS security update (Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4) to remediate the unauthorized iCloud storage access vulnerability.

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
macOSOperating system
Affected:>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 macOS version
    Run `sw_vers -productVersion` in Terminal or open System Settings > About
    Affected if The version is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3 (any version below 13.7.5, 14.7.5, or 15.4)
  2. Review enabled iCloud features
    Open System Settings > Apple ID > iCloud and compare against what you intentionally enabled
    Affected if iCloud Drive, iCloud Photos, iCloud Backup, or other iCloud features are enabled without your explicit consent
  3. Audit iCloud Drive configuration
    Check System Settings > iCloud > iCloud Drive and verify that only expected folders are syncing
    Affected if Unknown folders or unexpected directories are set to sync to iCloud Drive
  4. Examine iCloud Photos status
    Open System Settings > iCloud > Photos and verify the sync settings match your preferences
    Affected if Photos library sync is active but you did not intentionally enable it

You are affected if your macOS version falls within the vulnerable ranges AND you discover iCloud features enabled without your explicit authorization.

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 13.7.5 / 14.7.5 / 15.4 or later
Fixed in 13.7.514.7.515.4
Interim mitigation

Apply the appropriate macOS security update (Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4) to remediate the unauthorized iCloud storage access vulnerability.

Recommended fix High confidence

macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4 depending on currently installed version

  1. Open System Settings (or System Preferences on older macOS)
  2. Navigate to General > Software Update
  3. Check for available updates
  4. Install macOS 13.7.5 (if on Ventura), macOS 14.7.5 (if on Sonoma), or macOS 15.4 (if on Sequoia)
  5. Restart the system when prompted to complete the update
Caveat Point releases typically have minimal breaking changes; however, ensure critical applications are compatible before updating production systems

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

Fix this in macOS 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-2025-24207 — 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-24207 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