Secuno
ENNL
Book demo

CVE-2023-48082

Nagios Xi cross-site scripting (XSS)

9.1 CRITICALEPSS 1.54%
  1. Published14 Oct 2024

Description

Nagios XI before 2024R1 was discovered to improperly handle API keys generation (randomly-generated), allowing attackers to possibly generate the same set of API keys for all users and utilize them to authenticate.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Nagios Xi< 2014 · 2014

Remediation

Fixed in
Nagios Xi≥ 2014

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-928838.7
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 before…
CVE-2026-938868.3
IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote authenticated attacker to execute…
CVE-2026-1096338.1
Frappe ERPNext before 15.119.1 and 16.x before 16.32.0 contains a stored cross-site…
CVE-2025-714328.1
Frappe ERPNext before 14.92.1 and 15.x before 15.83.0 contains a reflected cross-site…
CVE-2026-1095588.7
EdgeEver 1.6.0 through 1.112.0 contains a stored cross-site scripting vulnerability in…
CVE-2026-1095578.7
EdgeEver through 1.112.0 contains a stored cross-site scripting vulnerability in…

Frequently asked

Is CVE-2023-48082 being actively exploited?

CVE-2023-48082 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.54%.

How severe is CVE-2023-48082?

CVE-2023-48082 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 1.54% probability of exploitation.

Which products are affected by CVE-2023-48082?

Affected products include Nagios Xi.

How do I fix CVE-2023-48082?

Upgrade affected software to a fixed version, for example Nagios Xi 2014 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2023-48082 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.