CVE-2022-43569 | Persistent Cross-Site Scripting via a Data Model object name in Splunk Enterprise

Exp

In Splunk Enterprise versions below 8.1.12, 8.2.9, and 9.0.2, an authenticated user can inject and store arbitrary scripts that can lead to persistent cross-site scripting (XSS) in the object name of a Data Model.

Published: 2022-11-04 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-43569 is rated High Exploit Risk (63.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.70%). 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-2022-43569

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

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

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.85% 0.70% -0.15%
2 2025-11-21 0.95% 0.85% -0.10%
3 2025-11-18 — 0.95% —

Full EPSS history (13 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.0 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H 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:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.1 5.9 [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-2022-43569

Affected software / configurations for CVE-2022-43569

Vendor Product Version Raw CPE
splunk splunk >= 8.1.0, < 8.1.12 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 8.2.0, < 8.2.9 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk >= 9.0.0, < 9.0.2 cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
splunk splunk_cloud_platform < 9.0.2209 cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*

References for CVE-2022-43569

cvelogic Threat Intelligence