AI security incident: LibreNMS /device-groups name Stored Cross-Site Scripting (GHSA-5pqf-54qp-32wx)
Summary **/device-groups name Stored Cross-Site Scripting** - HTTP POST - Request-URI(s): "/device-groups" - Vulnerable parameter(s): "name" - Attacker must be authenticated with "admin" privileges. - When a user adds a device group, an HTTP POST request is sent to the Request-URI "/device-groups". The name of the newly created device group is stored in the value of the name parameter. - After the device group is created, the entry is displayed along with some relevant buttons like Rediscover Devices, Edit, and Delete. ### Details The vulnerability exists as the name of the device group is not sanitized of HTML/JavaScript-related characters or strings.
Why This Is AI-Related
This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.
- Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.
Affected Workflow
Review the AI product, dependency, and integration points mentioned in the source advisory before broadening remediation.
Likely Attack Path
The advisory indicates a security path that can affect AI applications, assistants, models, or connected automation workflows if the component is deployed.
Impact
The advisory has meaningful security implications for an AI-related product, dependency, or workflow and should be triaged against deployed usage. Severity HIGH. Classification confidence 53%. Source channel GHSA.
Detection And Triage Signals
- New security events tied to the affected component or advisory identifier
- Changes in AI workflow behavior, access logs, or plugin execution after the advisory window
- Evidence that the vulnerable version is active in environments that process sensitive data
Recommended Response
- Confirm whether affected products, models, or integrations are used in your environment.
- Apply vendor fixes or mitigations and restrict risky permissions until verified.
- Monitor logs for related indicators and document containment for audit evidence.
Compliance And Business Impact
Even when exploit details are still emerging, delayed triage can widen operational and compliance exposure around AI systems.
Sources
Want alerts like this in real time?
Get notified with incident context, likely impact, and response guidance.
Get Notified