How severe is CVE-2023-49673?

CVE-2023-49673 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-49673?

CVE-2023-49673 affects the following packages: io.jenkins.plugins:neuvector-vulnerability-scanner (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-49673?

Update io.jenkins.plugins:neuvector-vulnerability-scanner to 2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49673 is resolved across your whole dependency graph.

How do I detect CVE-2023-49673 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:neuvector-vulnerability-scanner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-49673 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-49673 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-2023-49673?

CVE-2023-49673 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th 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-2023-49673?

CVE-2023-49673 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-49673 published, and has it been updated?

CVE-2023-49673 was published on November 29, 2023 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-49673 — neuvector-vulnerability-s…

HIGH

CVE-2023-49673 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in io.jenkins.plugins:neuvector-vulnerability-scanner. A fix is available for io.jenkins.plugins:neuvector-vulnerability-scanner — see the affected versions and patch details below.

Jenkins NeuVector Vulnerability Scanner Plugin Cross-Site Request Forgery vulnerability

Also known asGHSA-wpfc-r5qq-7r7p

Published

Nov 29, 2023

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-49673.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕io.jenkins.plugins:neuvector-vulnerability-scanner

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins NeuVector Vulnerability Scanner Plugin 1.22 and earlier does not perform a permission check in a connection test HTTP endpoint. This allows attackers with Overall/Read permission to connect to an attacker-specified hostname and port using attacker-specified username and password. Additionally, this HTTP endpoint does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

NeuVector Vulnerability Scanner Plugin 2.2 requires POST requests and Overall/Administer permission for the affected HTTP endpoint.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:neuvector-vulnerability-scanner`	all versions	2.2`io.jenkins.plugins:neuvector-vulnerability-scanner:2.2`

Affected Products

4 products · 4 configurations

Application

google compute enginejenkins

< 4.551.0

range

Application

jirajenkins

< 3.1.2

range

Application

matlabjenkins

< 2.11.1

range

Application

neuvector vulnerability scannerjenkins

< 2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:neuvector-vulnerability-scanner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:neuvector-vulnerability-scanner to 2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49673 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-49673 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 29, 2023

Last updated

Oct 24, 2026

Identifiers

CVE-2023-49673

GHSA-wpfc-r5qq-7r7p

References

Advisoryjenkins.io · 2023 11 29 Advisorynvd.nist.gov · CVE 2023 49673 Articleopenwall.com Packagegithub.com · neuvector vulnerability scanner plugin

Related vulnerabilities

Also affects neuvector-vulnerability-scanner

This CVE is high severity; 1 of 4 other CVEs affecting neuvector-vulnerability-scanner is rated as high or higher (top: high).

CVE-2023-49674CVE-2023-30517CVE-2022-43434CVE-2019-10430

Same weakness: CWE-352

This CVE is high severity — higher than any of the other 4 CVEs with CWE-352 (highest there: moderate).

CVE-2026-126067CVE-2026-109481CVE-2026-96629CVE-2026-118266Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2023-49673 — neuvector-vulnerability-s…

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-49673 in your dependencies?