CVE-2009-4898 twiki twiki: Cross Site Reference Forgery
twiki twiki: no CVSS score yet. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
Cross-site request forgery (CSRF) vulnerability in TWiki before 4.3.2 allows remote attackers to hijack the authentication of arbitrary users for requests that update pages, as demonstrated by a URL for a save script in the ACTION attribute of a FORM element, in conjunction with a call to the submit method in the onload attribute of a BODY element. NOTE: this issue exists because of an insufficient fix for CVE-2009-1339.
- EPSS
- 0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2009-4898 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2009-4898?via=ask-ai-copy and https://cve.bz/cve/CVE-2009-4898?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-2009-4898 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 4.3.1 |
| 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.0 |
| twiki:twiki | 4.2.1 |
| twiki:twiki | 4.2.2 |
| twiki:twiki | 4.2.3 |
| twiki:twiki | 4.2.4 |
| twiki:twiki | 4.3.0 |
Attack patterns (CAPEC)
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
- CAPEC-462 Cross-Domain Search Timing Severity: Medium
- CAPEC-467 Cross Site Identification Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.