{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14037 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-14037 and fix it if it is affected.\n\nWhat it is: CVE-2018-14037 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Sep 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-14037 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-14037/ (Markdown: https://insights.sbomify.com/CVE-2018-14037/index.md)","id":"CVE-2018-14037","markdown":"https://insights.sbomify.com/CVE-2018-14037/index.md","name":"CVE-2018-14037","record":{"aliases":["GHSA-h5vv-c2mv-8ccc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Kendo UI Editor","requires_auth":"none","summary":"Remote attackers can inject arbitrary JavaScript into the Kendo UI Editor, potentially executing code and taking over user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kendo_ui","vendor":"progress"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2018-14037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Bootstrap vulnerable to Cross-Site Scripting (XSS)","id":"CVE-2018-14040"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-14036"},"products":["n/a"],"published":"2018-09-28","related":[{"cvss_score":7.5,"headline":"MDX and SOAP Injection in Kendo UI for jQuery","id":"CVE-2026-108116","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":6.5,"headline":"Cross-site Scripting (XSS) in Kendo UI for jQuery FileBrowser and ImageBrowser","id":"CVE-2026-106163","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":5.4,"headline":"Cross-Site Scripting via ListBox Bound Text in Kendo UI for jQuery","id":"CVE-2026-106147","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":5.4,"headline":"Cross-Site Scripting via TabStrip, Menu, and PanelBar Image URLs in Kendo UI for jQuery","id":"CVE-2026-106148","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":5.4,"headline":"Cross-site Scripting (XSS) in Kendo UI for jQuery Menu","id":"CVE-2026-106149","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":5.4,"headline":"Cross-Site Scripting in Validator Validation Messages in Kendo UI for jQuery","id":"CVE-2026-106151","kev_date_added":null,"published":"2026-10-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can inject arbitrary JavaScript into the Kendo UI Editor, potentially executing code and taking over user sessions.","url":"https://insights.sbomify.com/CVE-2018-14037/"}