CVE-2023-1209

Cross-Site Scripting (XSS) vulnerabilities exist in ServiceNow records allowing an authenticated attacker to inject arbitrary scripts.

Published: 2023-05-23 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

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

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.73% 0.38% -0.36%
2 2026-06-08 1.41% 0.73% -0.68%
3 2026-06-05 — 1.41% —

Full EPSS history (16 records total)

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

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]
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]

Weakness enumeration for CVE-2023-1209

Affected software / configurations for CVE-2023-1209

Vendor Product Version Raw CPE
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:-:*:*:*:*:*:*
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_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_1_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_2b:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_10_hotfix_3b:*:*:*:*:*:*
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_3_hotfix_1:*:*:*:*:*:*
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_5_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_5_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_6_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_7_hotfix_1:*:*:*:*:*:*
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_8_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_8_hotfix_2:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9_hotfix_1:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9a:*:*:*:*:*:*
servicenow servicenow rome cpe:2.3:a:servicenow:servicenow:rome:patch_9b:*:*:*:*:*:*
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_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_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 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 utah cpe:2.3:a:servicenow:servicenow:utah:-:*:*:*:*:*:*

References for CVE-2023-1209

cvelogic Threat Intelligence