Security readout for executives and security teams
Plain-English summary
PNP4Nagios 0.6.26 is reported to store malicious script content through basket API and filter handling in the AJAX controller. If triggered in the monitoring interface, this could affect users viewing the stored content. Public sources do not provide CVSS, exploit status, or a named fixed release.
Executive priority
Treat this as a moderate monitoring-platform risk. Prioritize internet-exposed or broadly accessible PNP4Nagios instances, because stored XSS can undermine trust in operational dashboards even without confirmed active exploitation.
Technical view
CVE-2023-38350 describes stored cross-site scripting in PNP4Nagios through commit 81ebfc5, affecting 0.6.26. The reported locations are the AJAX controller, basket API, and filters. The available bundle cites PR #16 but does not confirm a release-level fix or detailed remediation.
Likely exposure
Exposure is likely limited to organizations running PNP4Nagios 0.6.26 or builds through 81ebfc5, especially where untrusted or lower-privileged users can save basket or filter data.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not state active exploitation. Stored XSS usually requires malicious data to be saved and later viewed by another user in the application.
Researcher notes
Evidence is sparse: no CVSS vector, CWE, CPE, exploit confirmation, or fixed release is provided in the bundle. Focus validation on affected version and commit exposure, stored data paths, and whether PR #16 or later maintained changes are deployed.
Mitigation direction
- Identify PNP4Nagios 0.6.26 or builds through commit 81ebfc5.
- Review the project PR and vendor guidance for confirmed fixed code or releases.
- Restrict PNP4Nagios access to trusted users and networks.
- Remove or sanitize suspicious saved basket and filter data.
- Monitor project advisories until remediation status is clear.
Validation and detection
- Confirm installed PNP4Nagios version and deployed commit level.
- Check whether changes associated with PR #16 are present.
- Review saved basket and filter records for unexpected script-like content.
- Confirm access controls limit who can create or modify filters.
- Document uncertainty where fix status cannot be proven.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2023-38350 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pnp4nagios/pnp4nagios/pull/16CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.