Skip to content
Fencer Intel
medium 4.3

CVE-2011-5025 json

Multiple cross-site scripting (XSS) vulnerabilities in the wiki application in Yaws 1.88 allow remote attackers to inject arbitrary web scr…

published 2011-12-29 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4930

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
2
Exploit-DB

Summary

Multiple cross-site scripting (XSS) vulnerabilities in the wiki application in Yaws 1.88 allow remote attackers to inject arbitrary web script or HTML via (1) the tag parameter to editTag.yaws, (2) the index parameter to showOldPage.yaws, (3) the node parameter to allRefsToMe.yaws, or (4) the text parameter to editPage.yaws.

Patch / fix

  • yaws Debian 14, Debian 13, Debian 12 1.92-1

debian advisories DEBIAN-CVE-2011-5025

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-5025 updated cvss 4.3

yaws: Stored and Reflective XSS in Yaws-Wiki

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-17111)
  2. Published

Exploit prediction

2.66% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-36498 Yaws-Wiki 1.88 - Multiple Cross-Site Scripting / HTML Injection Vulnerabilities webapps, 2012-01-05
  • EDB-17111 Yaws-Wiki 1.88-1 (Erlang) - Persistent / Reflective Cross-Site Scripting webapps, 2011-04-04

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.