PatchSiren cyber security CVE debrief
CVE-2017-6481 Phpipam CVE debrief
CVE-2017-6481 is a medium-severity cross-site scripting issue affecting phpipam 1.2. According to the NVD record, multiple pages accepted user-supplied data with insufficient filtration, including the instructions parameter in app/admin/instructions/preview.php and subnetId in app/admin/powerDNS/refresh-ptr-records.php. An attacker could cause a victim’s browser to execute arbitrary HTML and script in the context of the vulnerable phpipam site.
- Vendor
- Phpipam
- Product
- Unknown
- CVSS
- MEDIUM 6.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2017-03-05
- Original CVE updated
- 2026-05-13
- Advisory published
- 2017-03-05
- Advisory updated
- 2026-05-13
Who should care
Administrators and maintainers of phpipam deployments, especially those running version 1.2 or earlier branches covered by the NVD CPE range. Security teams should also care if these admin pages are reachable by authenticated users and if browsers can access the affected interfaces.
Technical summary
NVD describes the issue as CWE-79 (Cross-Site Scripting) with CVSS 3.0 vector CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The vulnerable input points identified in the record are the instructions parameter in app/admin/instructions/preview.php and subnetId in app/admin/powerDNS/refresh-ptr-records.php. Because the flaw is browser-executed script injection, successful exploitation depends on user interaction and can affect confidentiality and integrity within the vulnerable web origin.
Defensive priority
Medium
Recommended defensive actions
- Upgrade phpipam to a non-vulnerable release or apply the vendor fix referenced by the project issue tracker.
- Review app/admin/instructions/preview.php and app/admin/powerDNS/refresh-ptr-records.php for proper output encoding and input validation.
- Treat user-supplied values such as instructions and subnetId as untrusted and encode them before rendering in HTML contexts.
- Add or tighten server-side validation so that only expected formats and values are accepted.
- Audit administrator-facing workflows that render these fields and verify they do not reflect raw input into the browser.
- If feasible, deploy browser-side defense in depth such as a restrictive Content Security Policy to reduce script execution impact.
Evidence notes
This debrief is based on the NVD CVE record and its references. The record states that phpipam 1.2 is affected, identifies the vulnerable parameters and pages, and classifies the weakness as CWE-79 with CVSS 3.0 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The issue references include a SecurityFocus BID entry and a GitHub issue marked as Exploit and Vendor Advisory.
Sources and references
Verified primary and authoritative sources
-
CVE-2017-6481 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2017-6481
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2017-6481 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2017-6481
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/phpipam/phpipam/issues/992
[email protected] - Exploit, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.