CVE-2023-32445
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 · uneditedThis issue was addressed with improved checks. This issue is fixed in Safari 16.6, watchOS 9.6, iOS 15.7.8 and iPadOS 15.7.8, tvOS 16.6, iOS 16.6 and iPadOS 16.6, macOS Ventura 13.5. Processing a document may lead to a cross site scripting attack.
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 confidenceCross-site scripting (XSS) vulnerability in Safari and WebKit components across Apple devices (iOS, iPadOS, macOS, watchOS, tvOS). The vulnerability occurs when processing documents, allowing malicious scripts to be executed in the context of the user's session. The fix involves improved input validation/sanitization checks.
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< 16.6< 15.7.8>= 16.0, < 16.6< 15.7.8>= 16.0, < 16.6>= 13.0, < 13.5< 16.6< 9.6CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple device and browser typeDetermine whether the device is running Safari, iOS, iPadOS, macOS, tvOS, or watchOS. For macOS, check if Safari is the browser in use. On iOS/iPadOS, Safari is the underlying WebKit engine for all browsers.Affected if Device runs any of the affected Apple operating systems or Safari browser versions
-
Check Safari version on macOS or iOS/iPadOSOn macOS: Open Safari > Safari menu > About Safari. On iOS/iPadOS: Settings > Safari > About. Note the version number displayed.Affected if Safari version is earlier than 16.6
-
Check iOS versionGo to Settings > General > About. Note the iOS version number.Affected if iOS version is earlier than 15.7.8, OR between 16.0 and 16.5 (any version < 16.6)
-
Check iPadOS versionGo to Settings > General > About. Note the iPadOS version number.Affected if iPadOS version is earlier than 15.7.8, OR between 16.0 and 16.5 (any version < 16.6)
-
Check macOS versionClick Apple menu > About This Mac. Note the macOS version (Ventura 13.x).Affected if macOS Ventura version is 13.0 through 13.4 (any version < 13.5)
-
Check tvOS or watchOS versionOn tvOS: Settings > General > About > Version. On watchOS: Open the Watch app on iPhone > General > About > watchOS version.Affected if tvOS version is earlier than 16.6, OR watchOS version is earlier than 9.6
The environment is affected if any device runs Safari < 16.6, iOS/iPadOS < 15.7.8 or >= 16.0 and < 16.6, macOS Ventura 13.0-13.4, tvOS < 16.6, or watchOS < 9.6.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.613.515.7.8
Ensure all affected Apple devices are updated to the fixed versions (iOS/iPadOS 15.7.8+, iOS/iPadOS 16.6+, macOS Ventura 13.5+, Safari 16.6+, watchOS 9.6+, tvOS 16.6+). For web applications serving documents, implement Content Security Policy (CSP) headers and ensure proper output encoding as defense-in-depth.
iOS 15.7.8 / iOS 16.6, iPadOS 15.7.8 / iPadOS 16.6, macOS Ventura 13.5, watchOS 9.6, tvOS 16.6, Safari 16.6
- Open Settings app on iPhone or iPad, or System Preferences on Mac
- Navigate to General > Software Update (or System Preferences > Software Update on older macOS)
- Ensure automatic updates are enabled or manually check for updates
- Install the available security update: iOS 15.7.8 / iPadOS 15.7.8 for older devices, or iOS 16.6 / iPadOS 16.6 for newer devices
- For Mac users running macOS Ventura, update to version 13.5
- For Apple Watch users, update to watchOS 9.6
- For Apple TV users, update to tvOS 16.6
- For Safari standalone users on older macOS, update to Safari 16.6 via macOS update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-32445 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32445 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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