CVE-2018-14037: Cross-site scripting (XSS) vulnerability in Progress Kendo UI Editor v2018.1.221 allows remote attackers to inject arbitrary JavaScript into the DOM o...

Description

Cross-site scripting (XSS) vulnerability in Progress Kendo UI Editor v2018.1.221 allows remote attackers to inject arbitrary JavaScript into the DOM of the WYSIWYG editor because of the editorNS.Serializer toEditableHtml function in kendo.all.min.js. If the victim accesses the editor, the payload gets executed. Furthermore, if the payload is reflected at any other resource that does rely on the sanitisation of the editor itself, the JavaScript payload will be executed in the context of the application. This allows attackers (in the worst case) to take over user sessions.

Metrics

EPSS Probability

1.17%

63.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-79

Affected Software

Vendor	Product	Versions
Progress	Kendo Ui	2018.1.221

References

http://seclists.org/fulldisclosure/2018/Sep/49Mailing List, Third Party Advisory
http://seclists.org/fulldisclosure/2018/Sep/50Mailing List, Third Party Advisory
https://www.sec-consult.com/en/blog/advisories/stored-cross-site-scripting-in-kendo-ui-editor-cve-2018-14037/Exploit, Technical Description, Third Party Advisory
http://seclists.org/fulldisclosure/2018/Sep/49Mailing List, Third Party Advisory
http://seclists.org/fulldisclosure/2018/Sep/50Mailing List, Third Party Advisory
https://www.sec-consult.com/en/blog/advisories/stored-cross-site-scripting-in-kendo-ui-editor-cve-2018-14037/Exploit, Technical Description, Third Party Advisory

Timeline

Published: Sep 28, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2018-14037?

Cross-site scripting (XSS) vulnerability in Progress Kendo UI Editor v2018.1.221 allows remote attackers to inject arbitrary JavaScript into the DOM of the WYSIWYG editor because of the editorNS.Serializer toEditableHtml function in kendo.all.min.js. If the victim accesses the editor, the payload gets executed. Furthermore, if the payload is reflected at any other resource that does rely on the sanitisation of the editor itself, the JavaScript payload will be executed in the context of the application. This allows attackers (in the worst case) to take over user sessions.

How severe is CVE-2018-14037?

Severity scoring for CVE-2018-14037 is pending analysis. The EPSS model estimates a 1.17% probability of exploitation in the next 30 days.

How do I fix CVE-2018-14037?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2018

View all 2018CVEs →