CVE-2026-97818

8.6

phpIPAM · phpIPAM

phpIPAM through 1.8.3 contains an incorrect authorization vulnerability in the API controller, allowing unauthorized access to administrative functions.

Executive summary

An authorization bypass vulnerability in phpIPAM through 1.8.3 allows unauthorized users to access restricted administrative API endpoints, posing a significant risk to network management security.

Vulnerability

The vulnerability resides in the api/controllers/User.php file, where the application fails to properly enforce authorization checks for administrative roles. This flaw allows an unauthenticated attacker to interact with sensitive API controllers by manipulating the id parameter.

Business impact

Successful exploitation of this vulnerability can lead to unauthorized access to critical network documentation and management capabilities. Given the CVSS score of 8.6, this is classified as a high-severity issue that could result in full administrative control over the IP address management system, potentially facilitating further network reconnaissance or unauthorized configuration changes.

Remediation

Immediate Action: Update to the latest version of phpIPAM as provided in the vendor advisory at https://github.com/phpipam/phpipam/releases/tag/v1.8.3.

Proactive Monitoring: Monitor API access logs for anomalous requests targeting the User controller, particularly those attempting to access or modify administrative or global user lists.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized access to the /api/controllers/User.php endpoint.

Exploitation status

Public Exploit Available: No

Analyst recommendation

The severity of this authorization bypass necessitates immediate attention. Organizations should prioritize updating their phpIPAM instances to the latest version to prevent potential unauthorized administrative access to their network infrastructure.

More phpIPAM CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Analyst report updated
  5. Published in the daily brief high section

Sources