Perl Data::MuForm Module Has Unescaped HTML Rendering Vulnerability
Data::MuForm versions through 0.05 render attribute values and option labels into HTML without escaping, risking XSS.
30
Vulnerability1 · 1 read
CVE-2026-121632
XSS in Data::MuForm through 0.05
- CVSS 3.1
- 6.1 medium
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Data::MuForm versions through 0.05 for Perl render attribute values and option labels into HTML without escaping. An attacker can trigger this by supplying untrusted data to options_ methods, build_options methods or DBIC models. This allows embedding JavaScript in rendered pages. Applications using dynamic form options from untrusted data sources are affected.
What to do: Apply update for CVE-2026-121632
| Product | Affected |
|---|---|
| Perl Data::MuForm | through 0.05 |
Estimated exposure
nicheNo basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
Data::MuForm versions through 0.05 for Perl render attribute values and option labels into HTML without escaping. process_attrs writes each attribute value into the markup as is. The select, radio group and checkbox group renderers pass each option to it, so an option's value becomes an unescaped attribute. Option and option group labels are also unescaped, the group label inside a label attribute and the others in element content. Any application whose option list is built from data rather than literals, using an options_ method, a build_options method or a DBIC model, allows attacker-influenced text in an option value or label that can embed JavaScript in rendered pages. Attribute values built from data, such as through element_attr, are affected the same way.
- Weakness
- CWE-79
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N