Phpipam Vulnerabilities

Security vulnerability tracking for Phpipam Phpipam

Last updated: Mar 7, 2023
Total CVEs

3

Critical

0

With Exploits

2

Last 30 Days

0

Vulnerability Timeline

3 vulnerabilities discovered over time for Phpipam

Severity Distribution

Critical0
0%
High1
33%
Medium2
67%
Low0
0%
DescriptionVendor / ProductExploit Status
CVE-2023-12117.2

This vulnerability allows an attacker to manipulate the database of phpipam, potentially gaining access to sensitive information or altering data. It affects versions prior to 1.5.2 and requires the attacker to have the ability to send specially crafted requests to the application.

phpipamphpipam
Exploit Available
almost 3 years agoMar 7, 2023
CVE-2023-06766.1

This vulnerability allows an attacker to inject malicious scripts into web pages viewed by users of the phpipam application, potentially stealing sensitive information like session cookies. It occurs when users click on specially crafted links, and it affects versions prior to 1.5.1.

phpipamphpipam
Exploit Available
about 3 years agoFeb 4, 2023
CVE-2021-354386.1

This vulnerability allows an attacker to inject malicious scripts into the IP calculator feature of phpIPAM, which can then execute in the browser of anyone who visits the affected pages. To exploit this, the attacker needs to trick users into clicking on a specially crafted link that leads to the vulnerable pages.

phpipamphpipam
Theoretical
over 4 years agoJun 23, 2021

About Phpipam Phpipam Security

This page provides comprehensive security vulnerability tracking for Phpipam Phpipam. Our database includes all CVEs affecting this product, updated in real-time from official sources.

Each vulnerability listing includes detailed CVSS severity analysis, exploit availability status, AI-generated explanations, and direct links to official security patches and vendor advisories.

Security Recommendations

  • • Always keep Phpipam updated to the latest version
  • • Subscribe to security advisories from Phpipam
  • • Monitor this page for new vulnerabilities affecting your version
  • • Prioritize patching critical and high severity issues immediately