CVE-2024-38972: Vuln-Netbox · n/a
Affects Vuln-NetboxSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubminhquan202/Vuln-Netboxpkg:github/minhquan202/Vuln-NetboxOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-38972, organizations should implement the following specific measures: 1) Apply any official patches or updates from NetBox as soon as they become available. 2) In the absence of patches, implement web application firewall (WAF) rules to detect and block malicious payloads targeting the /dcim/power-ports/add/ endpoint, focusing on suspicious input in the Name parameter. 3) Enforce strict input validation and output encoding on all user-supplied data within the application, particularly for the affected parameter, to prevent script injection. 4) Limit user permissions to only those necessary, reducing the number of users who can access the vulnerable functionality. 5) Educate users about the risks of interacting with untrusted links or content within the NetBox interface to reduce the likelihood of successful user interaction exploitation. 6) Monitor application logs for unusual activity or repeated attempts to inject scripts. 7) Consider deploying Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts within the application context. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and parameter, user interaction requirements, and the operational context of NetBox.
Description
A cross-site scripting (XSS) vulnerability in netbox v4.0.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name parameter at /dcim/power-ports/add/.