# CVE-2026-7190: Reflected Cross-Site Scripting in ICT Innovations’ PHP-CGI/PHP-FPM configuration


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-874x-f28p-552g

## What is CVE-2026-7190?

CVE-2026-7190 is a medium-severity vulnerability in ICT Innovations’ PHP-CGI/PHP-FPM configuration, published on 29 Oct 2026. 

### Official description

A cross-site scripting (XSS) vulnerability in the ICTBroadcast software, which affects the demo environment. The vulnerability is found in the ‘login.php’ endpoint, where the ‘editForm[extension_username]’ parameter is reflected in the response without proper filtering. Successful exploitation of this vulnerability could allow an attacker to execute arbitrary JavaScript code in the victim’s browser once the victim accesses the malicious URL.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-7190 being exploited?

There is no known exploitation of CVE-2026-7190 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7190 is a medium-severity vulnerability in ICT Innovations’ PHP-CGI/PHP-FPM configuration, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-7190 in the wild and no public exploit code.

Affected product: ICT Innovations’ PHP-CGI/PHP-FPM configuration. 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-7190/ (Markdown: https://insights.sbomify.com/CVE-2026-7190/index.md)
```

## Sources

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

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