# CVE-2026-78190: WebDyne versions from 2.014 before 3.022 for Perl reflect request parameters unescaped into form field values, allowing cross-site scripting.


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-f457-wm99-2w49

## What is CVE-2026-78190?

CVE-2026-78190 is a medium-severity vulnerability in WebDyne, published on 31 Oct 2026. 

### Official description

WebDyne versions from 2.014 before 3.022 for Perl reflect request parameters unescaped into form field values, allowing cross-site scripting.

The textfield, password_field and filefield tags fill their value attribute from the request parameter of the same name. WEBDYNE_CGI_AUTOESCAPE, which controls escaping of these values, defaults to off. From 2.022, WebDyne::HTML::Tiny also replaced its entity_encode method with one that returns its input unchanged, so enabling WEBDYNE_CGI_AUTOESCAPE has no effect.

A remote attacker can inject script into any page using these tags through a crafted link.

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

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

1 open source package ship an affected version, including WebDyne.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `WebDyne` | cpan | `pkg:cpan/WebDyne` | From 2.014 | 3.022 |

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

Upgrade WebDyne to 3.022 or later.

## Is CVE-2026-78190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78190 is a medium-severity vulnerability in WebDyne, published on 31 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-78190 in the wild and no public exploit code.

Affected packages and fixed versions:
- WebDyne (cpan): affected from 2.014; fixed in 3.022

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-78190/ (Markdown: https://insights.sbomify.com/CVE-2026-78190/index.md)
```

## Sources

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

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