CVE-2010-3841 twiki twiki: Cross-site Scripting
twiki twiki: no CVSS score yet. EPSS 3.0% estimated probability of exploitation activity in the next 30 days.
On this page
Multiple cross-site scripting (XSS) vulnerabilities in lib/TWiki.pm in TWiki before 5.0.1 allow remote attackers to inject arbitrary web script or HTML via (1) the rev parameter to the view script or (2) the query string to the login script.
- EPSS
- 3.0% (unchanged from 3.0% a week ago; 3.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: http://twiki.org/cgi-bin/view/Codev/SecurityAlert-CVE-2010-3841
- Vendor advisory: http://secunia.com/advisories/41796
- Vendor advisory: http://twiki.org/cgi-bin/view/Codev/SecurityAlert-CVE-2010-3841
Ask an AI about this CVE
Show the prompt
Explain CVE-2010-3841 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2010-3841?via=ask-ai-copy and https://cve.bz/cve/CVE-2010-3841?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2010-3841 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| twiki:twiki | through 5.0.0 |
| twiki:twiki | 4.0.0 |
| twiki:twiki | 4.0.1 |
| twiki:twiki | 4.0.2 |
| twiki:twiki | 4.0.3 |
| twiki:twiki | 4.0.4 |
| twiki:twiki | 4.0.5 |
| twiki:twiki | 4.1.0 |
| twiki:twiki | 4.1.1 |
| twiki:twiki | 4.1.2 |
| twiki:twiki | 4.2.2 |
| twiki:twiki | 4.2.3 |
| twiki:twiki | 4.2.4 |
| twiki:twiki | 4.3.0 |
| twiki:twiki | 4.3.1 |
| twiki:twiki | 4.3.2 |
| twiki:twiki | 2000-12-01 |
| twiki:twiki | 2001-09-01 |
| twiki:twiki | 2001-12-01 |
| twiki:twiki | 2003-02-01 |
| twiki:twiki | 2004-09-01 |
| twiki:twiki | 2004-09-02 |
| twiki:twiki | 2004-09-03 |
| twiki:twiki | 2004-09-04 |
Public exploits
- Exploit-DB TWiki 5.0 - '/bin/view?rev' Cross-Site Scripting
- Exploit-DB TWiki 5.0 - bin/login Multiple Cross-Site Scripting Vulnerabilities
Attack patterns (CAPEC)
- CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
- CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
- CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
- CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
- CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
- CAPEC-592 Stored XSS Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.