dbcve.org
ChromeWeb browser · Google

CVE-2016-5147

MEDIUM · 6.1 CVSS v3.0 Published 2016-09-11
Fix available
A fix is available. Upgrade to after 52.0.2743.116 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Blink, as used in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, mishandles deferred page loads, which allows remote attackers to inject arbitrary web script or HTML via a crafted web site, aka "Universal XSS (UXSS)."

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

This is a Universal XSS (UXSS) vulnerability in the Blink rendering engine used by Google Chrome. The issue stems from improper handling of deferred page loads, which allows a malicious website to inject and execute arbitrary HTML or JavaScript in the context of other sites visited by the user, bypassing the same-origin policy.

MitigationUpdate Google Chrome to version 53.0.2785.89 or later on Windows/OS X, or version 53.0.2785.92 or later on Linux. This is a client-side browser vulnerability; no application code changes are required.

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
ChromeWeb browser
Affected:<= 52.0.2743.116

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Open Chrome version info
    Launch Google Chrome and navigate to chrome://version in the address bar, or click the three-dot menu > Help > About Google Chrome. Locate the full version number in the displayed information.
    Affected if Version number reads 52.0.2743.116 or lower (for example, 52.0.2743.100, 51.0.2623.110, etc.)
  2. Compare version components
    Parse the version string into four numeric parts separated by periods. Compare each part sequentially: the first part is the major version, followed by minor version, build number, and patch number. For example, in version 52.0.2743.116, the parts are 52, 0, 2743, and 116.
    Affected if The first numeric part is less than 52, OR it equals 52 but the second part is less than 0, OR the first two parts equal 52.0 but the third part is less than 2743, OR the first three parts equal 52.0.2743 and the fourth part is less than 116
  3. Confirm Chrome is the active browser
    Verify that Google Chrome is the browser in use. This vulnerability affects the Blink rendering engine within Chrome specifically, not other browsers regardless of version.
    Affected if Google Chrome is the installed browser and version falls within the affected range

If the installed Google Chrome version is 52.0.2743.116 or any version below it, the browser is vulnerable to this Universal XSS flaw.

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.

From vendor data
Upgrade available Upgrade to a release after 52.0.2743.116
Interim mitigation

Update Google Chrome to version 53.0.2785.89 or later on Windows/OS X, or version 53.0.2785.92 or later on Linux. This is a client-side browser vulnerability; no application code changes are required.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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