How severe is CVE-2022-45382?

CVE-2022-45382 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2022-45382?

CVE-2022-45382 affects the following products: jenkins naginator.

How do I patch CVE-2022-45382?

Apply the jenkins naginator security patch or hotfix for CVE-2022-45382 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2022-45382 across my infrastructure?

Inventory every jenkins naginator deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2022-45382 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2022-45382?

O3 detects and blocks CVE-2022-45382 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2022-45382 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-45382 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-45382?

CVE-2022-45382 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-45382?

CVE-2022-45382 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2022-45382?

CVE-2022-45382 affects jenkins naginator. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2022-45382 published, and has it been updated?

CVE-2022-45382 was published on November 15, 2022 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

MEDIUM severity

CVE-2022-45382

MEDIUM

CVE-2022-45382 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in jenkins naginator. O3 Security detects and blocks CVE-2022-45382 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

Jenkins Naginator Plugin 1.18.1 and earlier does not escape display names of source builds in builds that were triggered via Retry action, resulting in a stored cross-site scripting…

Published

Nov 15, 2022

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Jul 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2022-45382 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 356,453 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Description

Jenkins Naginator Plugin 1.18.1 and earlier does not escape display names of source builds in builds that were triggered via Retry action, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to edit build display names.

Affected Products

1 product · 1 configurations

Application

naginatorjenkins

< 1.18.2

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every jenkins naginator deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the jenkins naginator security patch or hotfix for CVE-2022-45382 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2022-45382 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2022-45382. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2022-45382 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2022-45382 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works