CVE-2019-8625
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 · uneditedA logic issue was addressed with improved state management. This issue is fixed in tvOS 13, iTunes for Windows 12.10.1, iCloud for Windows 10.7, iCloud for Windows 7.14. Processing maliciously crafted web content may lead to universal cross site scripting.
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 confidenceThis is a logic flaw in WebKit's state management that allows universal cross-site scripting (UXSS). The vulnerability enables an attacker to bypass the same-origin policy through maliciously crafted web content, potentially allowing access to sensitive data across different domains.
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< 7.14>= 10.0, < 10.7< 12.10.1< 2.26.4CVSS 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.
-
Check for Apple iCloud for Windows installationOpen Programs and Features or check C:\Program Files\Apple Inc.\iCloud\VersionInfo.xml for the installed version numberAffected if Version is less than 7.14 OR (version >= 10.0 AND less than 10.7)
-
Check for Apple iTunes for Windows installationOpen iTunes and go to Help > About iTunes, or check the version in Programs and FeaturesAffected if Version is less than 12.10.1
-
Check for WebKitGTK+ installation on Linux systemsRun 'webkitgtk-4.0-version' or 'dpkg -l libwebkit2gtk-4.0-37' (package name varies by distribution)Affected if Version is less than 2.26.4
-
Confirm WebKit is being used for renderingIdentify if the affected application uses WebKit as its HTML rendering engine (iCloud, iTunes, or WebKitGTK-based browsers)Affected if The application uses WebKit for rendering and the version is vulnerable
A user is affected if they have any of the vulnerable Apple products (iCloud for Windows or iTunes for Windows) or WebKitGTK+ installed with versions matching the affected ranges, and they browse malicious web content.
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.
From vendor data2.26.47.1410.7
Apply the vendor-supplied updates: tvOS 13, iTunes for Windows 12.10.1, iCloud for Windows 10.7/7.14, or later versions. This is a client-side vulnerability requiring endpoint updates.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8625 — 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-2019-8625 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