CVE-2019-20768

Exp

ServiceNow IT Service Management Kingston through Patch 14-1, London through Patch 7, and Madrid before patch 4 allow stored XSS via crafted sysparm_item_guid and sys_id parameters in an Incident Request to service_catalog.do.

Published: 2020-05-05 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-20768 is rated Exploit Available (54.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.72%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-20768

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-20768

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.21% 0.72% +0.51%
2 2026-01-18 0.28% 0.21% -0.07%
3 2025-11-21 — 0.28% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-20768

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.3 2.7 [email protected]
3.5 2.0 LOW
AV:N/AC:M/Au:S/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 6.8 2.9 [email protected]

Weakness enumeration for CVE-2019-20768

Affected software / configurations for CVE-2019-20768

Vendor Product Version Raw CPE
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:-:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_10:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_10-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_10-2:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_11:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_12:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_12-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_12-2:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_13:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_14:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_14-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_2:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_3:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_3-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_3-2:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_3a-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_4:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_4-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_4-2:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_4-4:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_5:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_6:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_6-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_6-2:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_6-3:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_6-5:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_7:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_7-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_8:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_8-1:*:*:*:*:*:*
servicenow it_service_management kingston cpe:2.3:a:servicenow:it_service_management:kingston:patch_9:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:-:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_1:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_1-2:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_1-3:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_2:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_2-2:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_2-4:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_2-5:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_3:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_3-3:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_3-4:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4-1:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4-2:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4-3:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4-4:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4-5:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_4-6:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_5:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_5-1:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_6:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_6-1:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_6a-1:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_6b-1:*:*:*:*:*:*
servicenow it_service_management london cpe:2.3:a:servicenow:it_service_management:london:patch_7:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:-:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_0-1:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_1:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_1-1:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_1-2:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_2:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_3:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_3-1:*:*:*:*:*:*
servicenow it_service_management madrid cpe:2.3:a:servicenow:it_service_management:madrid:patch_3-2:*:*:*:*:*:*

References for CVE-2019-20768

cvelogic Threat Intelligence