CVE-2022-46389 | Cross-Site Scripting (XSS) vulnerability found on logout functionality

There exists a reflected XSS within the logout functionality of ServiceNow versions lower than Quebec Patch 10 Hotfix 11b, Rome Patch 10 Hotfix 3b, San Diego Patch 9, Tokyo Patch 4, and Utah GA. This enables an unauthenticated remote attacker to execute arbitrary JavaScript code in the browser-based web console.

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

CVE-2022-46389 is rated Low Risk (39.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.60%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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

Exploit prediction scoring system (EPSS) score for CVE-2022-46389

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.68% 0.60% -0.08%
2 2026-05-20 1.02% 0.68% -0.34%
3 2026-04-19 — 1.02% —

Full EPSS history (34 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-46389

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/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:N)
No account or special rights needed—anonymous or random user is enough.
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.8 2.7 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/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:N)
No account or special rights needed—anonymous or random user is enough.
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.8 2.7 [email protected]

Weakness enumeration for CVE-2022-46389

Affected software / configurations for CVE-2022-46389

Vendor Product Version Raw CPE
servicenow servicenow quebec cpe:2.3:a:servicenow:servicenow:quebec:-:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:-:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:early_availability:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_1_hotfix_1b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_3:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_4_hotfix_1b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_5:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_8:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:-:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_1_hotfix_1b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_4:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_4a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_4b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_5:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_6:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_7:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_7b:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_8:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:-:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:early_availability:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_1:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_1a:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_1b:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_2:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_3:*:*:*:*:*:*
servicenow servicenow utah cpe:2.3:a:servicenow:servicenow:utah:-:*:*:*:*:*:*
servicenow servicenow utah cpe:2.3:a:servicenow:servicenow:utah:early_availability:*:*:*:*:*:*
servicenow servicenow utah cpe:2.3:a:servicenow:servicenow:utah:patch_1:*:*:*:*:*:*
servicenow servicenow utah cpe:2.3:a:servicenow:servicenow:utah:patch_2:*:*:*:*:*:*

References for CVE-2022-46389

cvelogic Threat Intelligence