CVE-2025-61078
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 · uneditedCross-site scripting (XSS) vulnerability in Request IP form in phpIPAM v1.7.3 allows remote attackers to inject arbitrary web script or HTML via the instructions parameter for the /app/admin/instructions/edit-result.php endpoint.
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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in phpIPAM v1.7.3 where the instructions parameter submitted to /app/admin/instructions/edit-result.php is not properly sanitized before storage and display. This allows authenticated attackers to inject arbitrary JavaScript or HTML that executes when administrators view the instructions.
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= 1.7.3CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm phpIPAM version is 1.7.3Check the version file (e.g., version.php in the root directory) or inspect the login page footer which typically displays the installed version. Alternatively, query the database for version information if accessible.Affected if The installed version is exactly 1.7.3
-
Verify admin access to instructions moduleLog in as an administrator and navigate to the instructions management area (typically /app/admin/instructions/ or via the admin menu). Confirm the edit-result.php endpoint exists and is accessible.Affected if User has administrative privileges and can access the instructions editing functionality
-
Inspect stored instructions in databaseAccess the phpIPAM database (MySQL/PostgreSQL) and query the instructions table. Look for any entries containing HTML tags (<script>, <img>, <iframe>, event handlers like onerror, onload) in the instruction content fields.Affected if The database contains unsanitized HTML or JavaScript in the instructions storage fields that could execute when rendered
-
Review application logs for injection attemptsCheck phpIPAM logs (typically in /log/ directory or database log tables) for requests to /app/admin/instructions/edit-result.php containing suspicious patterns like <script, javascript:, or encoded payloads.Affected if Recent requests to the edit-result.php endpoint contain XSS payload patterns in the instructions parameter
-
Test instructions output renderingIf you have admin access, view the instructions page (typically under Administration > Instructions) and inspect the page source to verify if stored content is properly escaped (look for < instead of <, etc.).Affected if Rendered output shows raw HTML/JavaScript without proper encoding (e.g., <script> appears as <script> instead of <script>)
You are affected if phpIPAM version 1.7.3 is installed AND the instructions table contains unsanitized XSS payloads that render unescaped in the admin instructions page.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and output encoding for the instructions parameter. Sanitize user input using appropriate HTML encoding functions before storing, and ensure all rendered output is properly escaped.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61078 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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