Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with high privileges to phpIPAM
-
ExploitCraft link to upgrade/index.php with payload in REQUEST_URI
-
ExecutionVictim follows crafted link, payload reflected
-
ImpactScript executes in victim's browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) high-privilege/administrative authentication to reach the upgrade/index.php endpoint (PR:H), and (2) user interaction - a victim must follow an attacker-crafted request whose REQUEST_URI value is reflected without sanitization (UI:P). The flaw is reflected XSS, not stored, so each exploitation needs a fresh lured request rather than a persistent payload. Limiting factors that reduce realistic risk: the attacker must already possess high privileges on the target instance, a separate user must be induced to act, impact is confined to low integrity (no data disclosure or service disruption per VC:N/VA:N), and the affected path is an upgrade utility rather than a routinely-used page. This is not a remote-unauthenticated issue against default configurations. |
| Impact | This is a low-priority issue, and the signals are consistent in saying so. The CVSS 4.0 base score is 1.9 (Low), and the vector (AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N) shows why: although the flaw is reachable over the network with low complexity, it requires high privileges (PR:H) and user interaction (UI:P), and its only impact is low integrity (VI:L) with no confidentiality or availability effect - consistent with a reflected cross-site scripting (CWE-79) bug. The vuln.today decision label is 'monitor', the exploit maturity is only E:P (proof-of-concept), and the lone exploit reference is a public gist that the input marks as 'not verified as working exploit code'. No EPSS score and no KEV listing were provided; absence of those is not evidence of risk here. There is no conflict among the signals: a high-privilege, user-interaction-dependent reflected XSS that yields only low integrity impact is a genuinely low-severity finding, not a high-CVSS-but-overrated one. The main caveat is sourcing - all data traces to a single reporter (VulDB) with no independent vendor advisory, so affected-version and trigger details are not corroborated. |
| Exploit ScenarioDerived | An attacker who already holds high-privilege (administrative) access to a phpIPAM instance crafts a URL to upgrade/index.php whose REQUEST_URI carries a script payload, then lures an authenticated user into following it; the value is reflected unsanitized and the script runs in the victim's browser session. A public PoC reference exists (a gist) but the input notes it is not verified as working exploit code, so practical weaponization is unconfirmed. The requirement for both high privileges and victim interaction makes opportunistic exploitation unlikely. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 24, 2026
phpIPAM through 1.8.3 contains a reflected cross-site scripting flaw in upgrade/index.php where the REQUEST_URI value is reflected without sanitization. Exploitation requires a high-privilege authenticated administrator to be lured into following a crafted request, and impact is limited to low integrity with no confidentiality or availability effect; a public PoC reference exists but is not verified as working exploit code, and the issue is rated low priority (monitor).
RemediationAI
The available data does not identify a vendor-released patch or fixed version for this issue; phpIPAM administrators should watch the VulDB entry (https://vuldb.com/vuln/426075) for an update. Until a fix is available, restrict access to upgrade/index.php to trusted administrative networks or localhost, since the endpoint is an upgrade utility that ordinary users do not need (trade-off: administrators must use an alternate access path such as a VPN or SSH tunnel). Where the application cannot be segmented, add a reverse-proxy or WAF rule that rejects script-bearing or encoded payloads in the request URI for that path (trade-off: possible false positives on legitimate encoded URLs). Treat the upgrade page as a high-privilege function and avoid following unsolicited links to it, because exploitation depends on a victim following a crafted request.
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 a PHP-based IP address management application. The flaw is CWE-79 (improper neutralization of input during web page generation), specifically reflected XSS in the upgrade utility's index.php, where the REQUEST_URI request value is echoed back into the response without sanitization. The trigger is described in the available sources as manipulation of the REQUEST_URI argument; the advisory does not specify further server-side preconditions. Because it is reflected rather than stored, each attempt requires a crafted request that a victim must follow. The affected path is an administrative upgrade page rather than a routine user-facing endpoint, and per the assessed vector the attacker must already hold high privileges (PR:H) and the victim must interact (UI:P). Impact is confined to low integrity (VI:L) with no confidentiality or availability impact.
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:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Reaching upgrade/index.php requires administrative access (PR:H) and a victim must follow a crafted link (UI:R); reflected XSS crosses into the browser context (S:C) with only low integrity impact and no confidentiality or availability effect.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security vulnerability has been detected in phpIPAM up to 1.8.3. Affected by this vulnerability is an unknown functionality of the file upgrade/index.php. Such manipulation of the argument REQUEST_URI leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure.
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
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
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-109318
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB