{"api_version":"1","generated_at":"2026-07-23T10:35:21+00:00","cve":"CVE-2019-17625","urls":{"html":"https://cve.report/CVE-2019-17625","api":"https://cve.report/api/cve/CVE-2019-17625.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2019-17625","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-17625"},"summary":{"title":"CVE-2019-17625","description":"There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2019-10-16 12:15:00","updated_at":"2019-10-16 22:36:00"},"problem_types":["CWE-79","CWE-78"],"metrics":[],"references":[{"url":"https://github.com/ramboxapp/community-edition/issues/2418","name":"https://github.com/ramboxapp/community-edition/issues/2418","refsource":"MISC","tags":["Exploit","Issue Tracking","Third Party Advisory"],"title":"Stored XSS vulnerability in Rambox 0.6.9 · Issue #2418 · ramboxapp/community-edition · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-17625","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-17625","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2019","cve_id":"17625","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"rambox","cpe5":"rambox","cpe6":"0.6.9","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"community","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"17625","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"rambox","cpe5":"rambox","cpe6":"0.6.9","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"community","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2019-17625","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://github.com/ramboxapp/community-edition/issues/2418","refsource":"MISC","name":"https://github.com/ramboxapp/community-edition/issues/2418"}]}},"nvd":{"publishedDate":"2019-10-16 12:15:00","lastModifiedDate":"2019-10-16 22:36:00","problem_types":["CWE-79","CWE-78"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"REQUIRED","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":9,"baseSeverity":"CRITICAL"},"exploitabilityScore":2.3,"impactScore":6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:S/C:C/I:C/A:C","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"SINGLE","confidentialityImpact":"COMPLETE","integrityImpact":"COMPLETE","availabilityImpact":"COMPLETE","baseScore":8.5},"severity":"HIGH","exploitabilityScore":6.8,"impactScore":10,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":true}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:rambox:rambox:0.6.9:*:*:*:community:*:*:*","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2019","CveId":"17625","Ordinal":"157499","Title":"CVE-2019-17625","CVE":"CVE-2019-17625","Year":"2019"},"notes":[{"CveYear":"2019","CveId":"17625","Ordinal":"1","NoteData":"There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element.","Type":"Description","Title":null},{"CveYear":"2019","CveId":"17625","Ordinal":"2","NoteData":"2019-10-16","Type":"Other","Title":"Published"},{"CveYear":"2019","CveId":"17625","Ordinal":"3","NoteData":"2019-10-16","Type":"Other","Title":"Modified"}]}}}