Skip to main content

phpIPAM EUVDEUVD-2026-109318

| CVE-2026-115981 LOW
Cross-site Scripting (XSS) (CWE-79)
2026-10-24 VulDB
1.9
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with high privileges to phpIPAM
  2. Exploit
    Craft link to upgrade/index.php with payload in REQUEST_URI
  3. Execution
    Victim follows crafted link, payload reflected
  4. Impact
    Script 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.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

phpipam 1.8.1
phpipam 1.8.2
phpipam 1.8.0
phpipam 1.8.3

Affected Packages

euvd phpipam no fix

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

Vendor (VulDB) PRIMARY 1.9 MEDIUM
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
vuln.today AI 3.4 LOW

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.

3.1 AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 24, 2026 - 22:24 NVD
MEDIUM LOW
CVSS changed
Oct 24, 2026 - 22:24 NVD
4.8 (MEDIUM) 1.9 (LOW)
CVE Published
Oct 24, 2026 - 21:45 cve.org
LOW 1.9

DescriptionCVE.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

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche open-source IP address management tool used mainly by network teams
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

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.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2022-41443 CRITICAL POC
9.8 Oct 03

phpipam v1.5.0 was discovered to contain a header injection vulnerability via the component /admin/subnets/ripe-query.ph

CVE-2019-16696 CRITICAL POC
9.8 Sep 22

phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/edit.php table parameter when action=add is used. Rated

CVE-2019-16695 CRITICAL POC
9.8 Sep 22

phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/filter.php table parameter when action=add is used. Rat

CVE-2019-16694 CRITICAL POC
9.8 Sep 22

phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/edit-result.php table parameter when action=add is used

CVE-2019-16693 CRITICAL POC
9.8 Sep 22

phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/order.php table parameter when action=add is used. Rate

CVE-2019-16692 CRITICAL POC
9.8 Sep 22

phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/filter-result.php table parameter when action=add is us

CVE-2018-1000869 CRITICAL POC
9.8 Dec 20

phpIPAM version 1.3.2 contains a CWE-89 vulnerability in /app/admin/nat/item-add-submit.php that can result in SQL Injec

CVE-2020-7988 HIGH POC
8.8 Mar 04

An issue was discovered in tools/pass-change/result.php in phpIPAM 1.4. Rated high severity (CVSS 8.8), this vulnerabili

CVE-2026-97818 HIGH POC
8.6 Sep 25

Incorrect authorization in phpIPAM's REST API (api/controllers/User.php) allows an attacker with API access to retrieve

CVE-2024-10718 HIGH POC
7.5 Mar 20

In phpipam/phpipam version 1.5.1, the Secure attribute for sensitive cookies in HTTPS sessions is not set. Rated high se

CVE-2023-41580 HIGH POC
7.5 Oct 02

Phpipam before v1.5.2 was discovered to contain a LDAP injection vulnerability via the dname parameter at /users/ad-sear

CVE-2023-1211 HIGH POC
7.2 Mar 07

SQL Injection in GitHub repository phpipam/phpipam prior to v1.5.2. Rated high severity (CVSS 7.2), this vulnerability i

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy