Security readout for executives and security teams
Plain-English summary
phpIPAM 1.3.2 and earlier has a login-page XSS issue tied to the phpipamredirect cookie. An attacker would need another weakness that lets them set or alter that cookie for the phpIPAM domain. The business concern is browser-side code execution against users of the IPAM portal, not direct server compromise from this CVE alone.
Executive priority
Treat this as a targeted remediation item, not an emergency by itself. Prioritize if phpIPAM is exposed to untrusted networks or if cookie-setting weaknesses exist on the same domain.
Technical view
The CVE states that the phpipamredirect cookie value is copied into an HTML tag on the login page inside single quotes, enabling XSS when attacker-controlled. Exploitability depends on chaining with a separate method to set or modify a cookie for the phpIPAM instance domain. No CVSS, CWE, patch version, or KEV listing is provided in the bundle.
Likely exposure
Exposure is limited to organizations running phpIPAM 1.3.2 or earlier, especially where the login page is reachable by untrusted users. Risk rises if another vulnerability or misconfiguration allows attacker-controlled cookies for the phpIPAM domain.
Exploitation context
The source bundle does not show active exploitation and KEV is false. The CVE explicitly says exploitation requires chaining with another issue that can set or modify the phpipamredirect cookie for the target domain.
Researcher notes
Evidence is sparse: the bundle provides the CVE description, CVE records, and a GitHub issue reference. The key research question is whether a practical cookie-setting vector exists in the target environment; without that chain, exploitability is constrained.
Mitigation direction
- Inventory phpIPAM deployments and identify versions 1.3.2 or earlier.
- Check phpIPAM vendor/project guidance for fixed releases or recommended remediation.
- Restrict phpIPAM login access to trusted networks, VPNs, or administrative users.
- Review domain and cookie controls to reduce attacker-controlled cookie opportunities.
- Monitor vendor issue 2338 and CVE records for remediation updates.
Validation and detection
- Confirm whether any phpIPAM instance is version 1.3.2 or earlier.
- Review login-page handling of the phpipamredirect cookie in deployed code.
- Check whether the login page is internet-accessible or broadly reachable internally.
- Review logs for suspicious login-page access patterns or abnormal cookie values.
- Verify compensating access controls are active around phpIPAM administration.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-1000860 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/phpipam/phpipam/issues/2338CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.