SafariWeb browser · Apple
CVE-2019-8674
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 iOS 13, Safari 13. 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 · moderate confidenceThis is a universal cross-site scripting (UXSS) vulnerability in Safari on iOS 13 and earlier versions. A logic error in state management allows processing of maliciously crafted web content to bypass same-origin restrictions, enabling injection of arbitrary JavaScript into any website the victim visits.
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
< 13< 13.0< 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 iOS version on iPhone or iPadGo to Settings > General > About and look at the Version fieldAffected if Version is earlier than 13.0 (e.g., 12.x, 11.x, etc.)
-
Check Safari version on iOSOpen Safari, go to Settings > Safari > About, or check via iTunes/Finder when device is connectedAffected if Safari version is earlier than 13.0 on iOS 13 or earlier systems
-
Check WebKitGTK version on Linux systemsRun `dpkg -l libwebkit2gtk-4.0-37` or `rpm -qa | grep webkit2gtk` to query the installed package versionAffected if Version is earlier than 2.26.4
-
Verify browser is processing web contentThe vulnerability is triggered when Safari processes malicious web content; no special configuration check needed - the mere use of a vulnerable Safari version on iOS or WebKitGTK < 2.26.4 enables the attack surfaceAffected if Any use of affected Safari versions (< 13) or WebKitGTK versions (< 2.26.4) while browsing the internet
A user is affected if they run Safari versions earlier than 13 on iOS systems earlier than 13.0, or WebKitGTK versions earlier than 2.26.4 on Linux, and browse the web where malicious content could be encountered.
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.41313.0
Users should update Safari to version 13 or later (iOS 13) to receive the patch. Organizations may consider implementing browser update policies and warning users who cannot update immediately.
Fix this in Safari
Scoped from the published advisory
- Consultation1.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-2019-8674 — 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-8674 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