dbcve.org
PhpipamApplication

CVE-2017-15640

MEDIUM · 5.4 CVSS v3.0 Published 2018-04-21
Fix available
A fix is available. Upgrade to 1.3.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
app/sections/user-menu.php in phpIPAM before 1.3.1 has XSS via the ip parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-site scripting (XSS) vulnerability in phpIPAM before version 1.3.1 in the app/sections/user-menu.php file. The 'ip' parameter is not properly sanitized, allowing injection of malicious JavaScript code through user-supplied input.

MitigationUpdate phpIPAM to version 1.3.1 or later. Alternatively, implement proper input validation and output encoding on the 'ip' parameter in user-menu.php to sanitize user input before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PhpipamApplication
Affected:< 1.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed phpIPAM version
    Locate the version file or check the database configuration for the phpIPAM version number. Common locations include a VERSION file in the root directory, a config file, or the database itself.
    Affected if The installed version is before 1.3.1
  2. Verify vulnerable file exists
    Check if the file app/sections/user-menu.php exists in the phpIPAM installation directory.
    Affected if The file exists and the application uses this component
  3. Inspect the ip parameter handling in user-menu.php
    Open app/sections/user-menu.php and locate code that handles the ip parameter from user input. Check if the value is used in HTML output without sanitization functions like htmlspecialchars().
    Affected if The ip parameter is output without proper sanitization or encoding
  4. Test ip parameter for XSS vulnerability
    If the application accepts an ip parameter through GET or POST requests to user-menu.php, submit a benign test payload and observe if it is reflected in the response unescaped.
    Affected if User-supplied ip values are reflected in the page without being encoded

A system is affected if phpIPAM version is below 1.3.1 and the ip parameter in app/sections/user-menu.php is not sanitized before output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.3.1 or later
Fixed in 1.3.1
Interim mitigation

Update phpIPAM to version 1.3.1 or later. Alternatively, implement proper input validation and output encoding on the 'ip' parameter in user-menu.php to sanitize user input before rendering.

Fix this in Phpipam Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15640 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data