# CVE-2026-115981: phpIPAM index.php cross site scripting


- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-f44p-5m2h-hc4x

## What is CVE-2026-115981?

CVE-2026-115981 is a medium-severity vulnerability in phpIPAM, published on 24 Oct 2026. 

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-115981?


## How do I fix CVE-2026-115981?

No fix has been published for CVE-2026-115981 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115981 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115981 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115981 and fix it if it is affected.

What it is: CVE-2026-115981 is a medium-severity vulnerability in phpIPAM, published on 24 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115981 exists.

Affected product: phpIPAM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115981/ (Markdown: https://insights.sbomify.com/CVE-2026-115981/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115981
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115981
- OSV: https://osv.dev/vulnerability/CVE-2026-115981

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115981/
Summaries are generated and may contain mistakes; the official description above is the record.