AI security incident: LibreNMS has a Stored XSS in Custom OID - unit parameter missing strip_tags() (GHSA-f...
Summary The unit parameter in Custom OID functionality lacks strip_tags() sanitization while other fields ( name , oid , datatype ) are sanitized. The unsanitized value is stored in the database and rendered without HTML escaping, allowing Stored XSS. ### Details **Vulnerable Input Processing ( includes/html/forms/customoid.inc.php lines 18-21):** php $name = strip_tags((string) $_POST['name']); // line 18 - SANITIZED $oid = strip_tags((string) $_POST['oid']); // line 19 - SANITIZED $datatype = strip_tags((string) $_POST['datatype']); // line 20 - SANITIZED $unit = $_POST['unit']; // line 21 - NOT SANITIZED! **Vulnerable Output ( graphs/customoid.inc.
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 issue can weaken identity or authorization boundaries around AI features, plugins, or operator workflows. 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
- Audit the affected AI workflow for exposed admin actions, service tokens, and user-to-tool permissions.
- Rotate or disable sensitive credentials if the issue could weaken authentication or authorization boundaries.
- Review access logs for unusual account actions, scope changes, or integrations created after disclosure.
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