cve.bz

CVE-2009-1339 twiki twiki: Cross Site Reference Forgery

no score yetExploit referenceEPSS 0.8%Fix available

twiki twiki: no CVSS score yet. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Cross-site request forgery (CSRF) vulnerability in TWiki before 4.3.1 allows remote authenticated users to hijack the authentication of arbitrary users for requests that update pages, as demonstrated by a URL for a save script in the SRC attribute of an IMG element, a related issue to CVE-2009-1434.
EPSS
0.8% (unchanged from 0.8% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th 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

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2009-1339 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2009-1339?via=ask-ai-copy and https://cve.bz/cve/CVE-2009-1339?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-1339 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.

ProductAffected
twiki:twikithrough 4.3.0
twiki:twiki4.1.2
twiki:twiki4.2.0
twiki:twiki4.2.1
twiki:twiki4.2.2
twiki:twiki4.2.3
twiki:twiki4.2.4

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.

References

Check your stackJSON