CVE-2023-1298

ServiceNow has released upgrades and patches that address a Reflected Cross-Site scripting (XSS) vulnerability that was identified in the ServiceNow Polaris Layout. This vulnerability would enable an authenticated user to inject arbitrary scripts.

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

CVE-2023-1298 is rated Low Risk (25.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.34%). 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-2023-1298

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 1.15% 0.34% -0.81%
2 2026-03-31 0.92% 1.15% +0.23%
3 2026-03-04 — 0.92% —

Full EPSS history (35 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-1298

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/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:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [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-2023-1298

Affected software / configurations for CVE-2023-1298

Vendor Product Version Raw CPE
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_2_hotfix_1:*:*:*:*:*:*
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_3_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_3:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_3_hotfix_4:*:*:*:*:*:*
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_7_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_7_hotfix_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_7_hottix_3:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_7a:*:*:*:*:*:*
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 san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_8_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_8_hotfix_2:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_9:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_9a:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_9a_hotfix_1:*:*:*:*:*:*
servicenow servicenow san_diego cpe:2.3:a:servicenow:servicenow:san_diego:patch_9b:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:-:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_1:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_1_hotfix_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_2_hotfix_1:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_2_hotfix_2:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_2_hotfix_3:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_2_hotfix_4:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_3:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_3_hotfix_1:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_3_hotfix_2:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_3_hotfix_3:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_3_hotfix_4:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_4:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_4_hotfix_2:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_4_hotfix_3:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_4a:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_4a_hotfix_1:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_5:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_5_hotfix_1:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_5_hotfix_2:*:*:*:*:*:*
servicenow servicenow tokyo cpe:2.3:a:servicenow:servicenow:tokyo:patch_5_hotfix_3:*:*:*:*:*:*
servicenow servicenow utah cpe:2.3:a:servicenow:servicenow:utah:patch_1:*:*:*:*:*:*

References for CVE-2023-1298

cvelogic Threat Intelligence