{"id":"CVE-2019-16991","url":"https://www.cyber-defence.io/tools/cve/CVE-2019-16991","generatedAt":"2026-10-27T23:28:26.575Z","title":"In FusionPBX up to v4.5.7, the file app\\edit\\filedelete.php uses an unsanitized \"file\" variable coming from the URL, which is reflected in HTML, leading to XSS.","description":"In FusionPBX up to v4.5.7, the file app\\edit\\filedelete.php uses an unsanitized \"file\" variable coming from the URL, which is reflected in HTML, leading to XSS.","published":"2019-10-21T16:15:18.000Z","lastModified":"2026-06-17T02:23:06.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.1","score":6.1,"severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"},"cwe":["CWE-79"],"affected":["fusionpbx/fusionpbx"],"epss":{"score":0.00803,"percentile":0.56434,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.80%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://github.com/fusionpbx/fusionpbx/commit/cd4632b46c62855f7e1c1c93d20ffd64edcb476e","tags":["Patch"],"source":"cve@mitre.org"},{"url":"https://resp3ctblog.wordpress.com/2019/10/19/fusionpbx-xss-20/","tags":["Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://github.com/fusionpbx/fusionpbx/commit/cd4632b46c62855f7e1c1c93d20ffd64edcb476e","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://resp3ctblog.wordpress.com/2019/10/19/fusionpbx-xss-20/","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-16991","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}