CVE-2024-41355: phpipam · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 26 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 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-41355, organizations should implement the following specific measures: 1) Apply input validation and output encoding on all user-supplied data in the /app/tools/request-ip/index.php endpoint to neutralize malicious scripts. 2) Restrict access to the vulnerable endpoint to trusted users only, using network segmentation or access control lists. 3) Enforce strong authentication and monitor for unusual user activity that could indicate exploitation attempts. 4) If patches become available, prioritize timely updates of phpipam to the fixed version. 5) Employ Content Security Policy (CSP) headers to limit the impact of potential XSS payloads. 6) Conduct regular security assessments and penetration tests focusing on web application vulnerabilities. 7) Educate users about the risks of interacting with suspicious links or inputs within the IPAM interface. These measures go beyond generic advice by focusing on the specific vulnerable component and operational context.
Description
phpipam 1.6 is vulnerable to Cross Site Scripting (XSS) via /app/tools/request-ip/index.php.