CVE-2019-12592
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 universal Cross-site scripting (UXSS) vulnerability in the Evernote Web Clipper extension before 7.11.1 for Chrome allows remote attackers to run arbitrary web script or HTML in the context of any loaded 3rd-party IFrame.
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 confidenceA universal XSS (UXSS) vulnerability in the Evernote Web Clipper Chrome extension before version 7.11.1 allows the extension to execute arbitrary JavaScript or HTML within the context of any third-party IFrame loaded in the browser. This occurs due to improper sanitization or validation of content from IFrames, allowing an attacker who can control IFrame content to escape the IFrame context and execute code in the extension's broader origin.
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.11.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Evernote Web Clipper is installedOpen Chrome and navigate to chrome://extensions, or on Windows check the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Google\Chrome\Extensions or HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\Extensions for extension ID lbjhdepnnhdmjbgfmmobhlnbppknaoao (Evernote Web Clipper)Affected if The extension ID lbjhdepnnhdmjbgfmmobhlnbppknaoao is found in Chrome's extension list or registry
-
Retrieve the installed extension versionIn Chrome, go to chrome://extensions and enable Developer Mode, then find the Evernote Web Clipper entry to view its version number, or inspect the manifest.json file in the extension's install directoryAffected if A version number is displayed for the Evernote Web Clipper extension
-
Compare version against vulnerable rangeCompare the installed version number to 7.11.1 - any version less than 7.11.1 (such as 7.11.0, 7.10.x, etc.) is vulnerableAffected if The installed version is below 7.11.1 (e.g., 7.10.0, 7.9.2, etc.)
-
Verify the extension is enabledIn Chrome, go to chrome://extensions and confirm the Evernote Web Clipper toggle is turned ON, or check if the extension icon appears in the Chrome toolbarAffected if The extension is installed and currently enabled in the browser
If Evernote Web Clipper extension version 7.11.1 or higher is installed and disabled, the user is not affected; otherwise, the universal XSS vulnerability is present.
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 data7.11.1
Update the Evernote Web Clipper Chrome extension to version 7.11.1 or later. Organizations should verify that managed browsers have the updated extension deployed.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12592 — 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-12592 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