phpIPAM vulnerabilities
We track 5 vulnerabilities in phpIPAM products across 2 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on August 24, 2026.
Latest phpIPAM vulnerabilities
- 9.1 Critical severity
phpipam: Use of Incorrectly-Resolved Name or Reference
phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access by exploiting an insecure object cache keying mechanism. The cache is keyed by lookup value alone without includi
- 7.5 High severity
phpipam: Authorization Bypass Through User-Controlled Key
phpIPAM through 1.8.1 fails to verify that a requested IP address belongs to the subnet a temporary share token was issued for. In app/temp_share/index.php and app/temp_share/address.php, when the share type is 'subnets', the subnetId parameter is used directl
- 7.5 High severity
phpipam/phpipam: Cleartext Transmission of Sensitive Information
In phpipam/phpipam version 1.5.1, the Secure attribute for sensitive cookies in HTTPS sessions is not set. This could cause the user agent to send those cookies in plaintext over an HTTP session, potentially exposing sensitive information. The issue is fixed i
- 7.5 High severity
Phpipam: Improper Neutralization of Special Elements in Output Used by a Downstream Component
Phpipam before v1.5.2 was discovered to contain a LDAP injection vulnerability via the dname parameter at /users/ad-search-result.php. This vulnerability allows attackers to enumerate arbitrary fields in the LDAP server and access sensitive data via a crafted
- 7.2 High severity
PhpIPAM: Improper Neutralization of Special Elements used in an SQL Command
PhpIPAM v1.4.4 allows an authenticated admin user to inject SQL sentences in the "subnet" parameter while searching a subnet via app/admin/routing/edit-bgp-mapping-search.php