CVE-2020-15092

In TimelineJS before version 3.7.0, some user data renders as HTML. An attacker could implement an XSS exploit with maliciously crafted content in a number of data fields. This risk is present whether the source data for the timeline is stored on Google Sheets or in a JSON configuration file. Most TimelineJS users configure their timeline with a Google Sheets document. Those users are exposed to this vulnerability if they grant write access to the document to a malicious inside attacker, if the access of a trusted user is compromised, or if they grant public write access to the document. Some TimelineJS users configure their timeline with a JSON document. Those users are exposed to this vulnerability if they grant write access to the document to a malicious inside attacker, if the access of a trusted user is compromised, or if write access to the system hosting that document is otherwise compromised. Version 3.7.0 of TimelineJS addresses this in two ways. For content which is intended to support limited HTML markup for styling and linking, that content is "sanitized" before being added to the DOM. For content intended for simple text display, all markup is stripped. Very few users of TimelineJS actually install the TimelineJS code on their server. Most users publish a timeline using a URL hosted on systems we control. The fix for this issue is published to our system such that **those users will automatically begin using the new code**. The only exception would be users who have deliberately edited the embed URL to "pin" their timeline to an earlier version of the code. Some users of TimelineJS use it as a part of a wordpress plugin (knight-lab-timelinejs). Version 3.7.0.0 of that plugin and newer integrate the updated code. Users are encouraged to update the plugin rather than manually update the embedded version of TimelineJS.

• CWE-79
• CWE-79

• https://github.com/NUKnightLab/TimelineJS3/security/advisories/GHSA-2jpm-827p-j44gPatch, Third Party Advisory
• https://knightlab.northwestern.edu/posts/Vendor Advisory
• https://github.com/NUKnightLab/TimelineJS3/security/advisories/GHSA-2jpm-827p-j44gPatch, Third Party Advisory
• https://knightlab.northwestern.edu/posts/Vendor Advisory

Published

Jul 9, 2020

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2020-15084In express-jwt (NPM package) up and including version 5.3.3,…9.1
• CVE-2020-15085In Saleor Storefront before version 2.10.3, request data use…6.1
• CVE-2020-15086In TYPO3 installations with the "mediace" extension from ver…9.8
• CVE-2020-15087In Presto before version 337, authenticated users can bypass…8.8
• CVE-2020-1509An elevation of privilege vulnerability exists in the Local …7.8
• CVE-2020-15091TenderMint from version 0.33.0 and before version 0.33.6 all…6.5
• CVE-2020-15093The tough library (Rust/crates.io) prior to version 0.7.1 do…8.6
• CVE-2020-15094In Symfony before versions 4.4.13 and 5.1.5, the CachingHttp…8.8
• CVE-2020-15095Versions of the npm CLI prior to 6.14.6 are vulnerable to an…4.4
• CVE-2020-15096In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-b…6.8
• CVE-2020-15097loklak is an open-source server application which is able to…9.1
• CVE-2020-15098In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.…8.8