# CVE-2026-46594: Reflected XSS in PHP Poll Script


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-4m43-9f84-rm49

## What is CVE-2026-46594?

CVE-2026-46594 is a medium-severity vulnerability in PHP Poll Script, published on 31 Jul 2026. 

### Official description

A reflected cross-site scripting (XSS) vulnerability has been identified in the PHP Jabbers - PHP Poll Script. A malicious attacker can craft a specially crafted URL that, when opened, results in arbitrary JavaScript execution in the victim's browser.
This issue was fixed in version 4.1.

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

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


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

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

## Is CVE-2026-46594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46594 is a medium-severity vulnerability in PHP Poll Script, published on 31 Jul 2026. 
Exploitation: There is no known exploitation of CVE-2026-46594 in the wild and no public exploit code.

Affected product: PHP Poll Script. 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-46594/ (Markdown: https://insights.sbomify.com/CVE-2026-46594/index.md)
```

## Sources

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

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