Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege phpIPAM user
-
ExploitRequest customer/location/NAT tool pages
-
ExecutionMissing check_permission allows access
-
ImpactRead restricted IPs, CIDRs, hostnames and MACs
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated phpIPAM account with low privileges (CVSS PR:L) - there is no unauthenticated path. Given such an account, exploitation works against default code in phpIPAM through 1.8.3: the customers (objects.php/ipaddresses.php), single-location.php, and nat_details.php pages do not invoke Subnets::check_permission, so no special configuration or feature toggle is needed. Limiting factors: the attacker must already possess credentials; no user interaction is required; impact is strictly read-only disclosure of network inventory data (IPs, CIDRs, hostnames, MACs) and does not grant write access, code execution, or availability impact. |
| Impact | This is a genuine but moderate-severity issue, not a top-tier priority. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N, 5.3 Medium) is internally consistent with the description: a network-reachable, low-complexity flaw that nonetheless requires an authenticated low-privilege account (PR:L) and yields only limited confidentiality impact (VC:L) with no integrity or availability effect. The CWE-862 (Missing Authorization) classification aligns cleanly with the described behavior - specific tool pages skip Subnets::check_permission - so there is no conflict between the vector and the narrative. No EPSS score was provided in the input, so exploitation probability cannot be quantified. KEV status is not present in the input, so this is not confirmed as actively exploited. A detailed public write-up (hackmd) and exact vulnerable source-line references exist, lowering the barrier to exploitation even though no weaponized exploit tool is cited. Net real-world risk: a post-authentication horizontal information-disclosure bug that leaks network inventory data to users who already have some access - valuable for internal reconnaissance/privilege-boundary violations but gated behind authentication and limited to read-only data exposure, so it ranks below unauthenticated or code-execution flaws. |
| Exploit ScenarioDerived | A low-privilege phpIPAM user (or an attacker who has phished/obtained such an account) who is only authorized for a subset of sections directly requests tools/customers objects.php, tools/locations/single-location.php, or tools/nat/nat_details.php. Because these pages omit the Subnets::check_permission call, the server returns IP addresses, CIDRs, hostnames, and MAC addresses from subnets and sections the user was never granted access to. A public technical write-up documents the exact pages and lines involved, making the technique trivial to reproduce even without packaged exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Authenticated low-privilege users of phpIPAM through 1.8.3 can read restricted subnet and address data via the customer, location, and NAT tool pages, which omit the Subnets::check_permission authorization check (CWE-862). This moderate-severity issue requires a valid low-privilege account (CVSS 4.0 5.3, PR:L) and enables read-only disclosure of IP addresses, CIDRs, hostnames, and MAC addresses from sections the user is not authorized to view; there is no unauthenticated path, no write or code execution impact, and no public exploit identified at time of analysis. A public technical writeup describing the cross-section address disclosure is referenced, but this is not a top-tier priority.
RemediationAI
No vendor-released patch identified at time of analysis; patch status is not confirmed from the provided data. Monitor the phpIPAM repository (https://github.com/phpipam/phpipam) and the VulnCheck advisory for an official fix, and upgrade beyond 1.8.3 when a patched release becomes available. As a compensating control, restrict access to the affected endpoints (/app/tools/customers/customer/objects/ipaddresses.php, /app/tools/locations/single-location.php, /app/tools/nat/nat_details.php) to trusted administrative roles via web server ACLs, reverse proxy rules, or WAF policies; trade-off: low-privilege users lose access to these specific tools pages, which may break intended read-only workflows, so validate business requirements. Alternatively, apply a temporary code patch that adds Subnets::check_permission at the start of those three scripts, mirroring the authorization pattern used elsewhere in phpIPAM; this is unsupported and requires testing before deployment. Also audit logs for access to those endpoints to detect attempted abuse, and enforce least privilege by reviewing user roles to minimize the number of low-privilege accounts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
phpIPAM is an open-source PHP-based IP address management (IPAM) web application. The vulnerability is a missing authorization flaw (CWE-862) in three tool pages: app/tools/customers/customer/objects/ipaddresses.php (lines 69-110), app/tools/locations/single-location.php (lines 129-195), and app/tools/nat/nat_details.php (lines 16-45), which fail to invoke Subnets::check_permission before returning subnet, address, hostname, and MAC data. The CPE cpe:2.3:a:phpipam:phpipam:*:*:*:*:*:*:*:* with the advisory scope 'through 1.8.3' indicates all versions up to and including 1.8.3 are affected. The assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N confirms network exploitable, low privileges required, no user interaction, and limited confidentiality impact only. A public HackMD writeup and the VulnCheck advisory document the issue, but the input does not identify a fixed release.
Know when Phpipam gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable page requests requiring an authenticated low-privilege account give AV:N/AC:L/PR:L/UI:N; impact is limited read-only data disclosure, so C:L with I:N/A:N and unchanged scope.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
phpIPAM through 1.8.3 contains a missing authorization vulnerability that allows authenticated low-privilege users to view restricted subnets and addresses because customer, location and NAT pages skip Subnets::check_permission. Attackers can open customer objects.php, single-location.php or nat_details.php to read IP addresses, CIDRs, hostnames and MAC addresses from sections they cannot access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
phpipam v1.5.0 was discovered to contain a header injection vulnerability via the component /admin/subnets/ripe-query.ph
phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/edit.php table parameter when action=add is used. Rated
phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/filter.php table parameter when action=add is used. Rat
phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/edit-result.php table parameter when action=add is used
phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/order.php table parameter when action=add is used. Rate
phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/filter-result.php table parameter when action=add is us
phpIPAM version 1.3.2 contains a CWE-89 vulnerability in /app/admin/nat/item-add-submit.php that can result in SQL Injec
An issue was discovered in tools/pass-change/result.php in phpIPAM 1.4. Rated high severity (CVSS 8.8), this vulnerabili
Incorrect authorization in phpIPAM's REST API (api/controllers/User.php) allows an attacker with API access to retrieve
In phpipam/phpipam version 1.5.1, the Secure attribute for sensitive cookies in HTTPS sessions is not set. Rated high se
Phpipam before v1.5.2 was discovered to contain a LDAP injection vulnerability via the dname parameter at /users/ad-sear
SQL Injection in GitHub repository phpipam/phpipam prior to v1.5.2. Rated high severity (CVSS 7.2), this vulnerability i
EUVD-2026-96994
GHSA-rv8q-2v6x-vpgr
NVD
CVE.org
EPSS
Exploit-DB