CVE-2024-39063: Cross-Site Request Forgery (CSRF)
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-39063, organizations should implement the following specific actions: 1) Immediately restrict access to Lime Survey instances to trusted networks or VPNs to reduce exposure. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious GET requests that attempt to perform state-changing actions or include parameters typically protected by CSRF tokens. 3) Educate users and administrators to avoid clicking on untrusted links and to verify URLs before accessing Lime Survey resources. 4) Monitor server logs for unusual GET request patterns that could indicate exploitation attempts. 5) If possible, configure Lime Survey or the underlying Yii framework to enforce CSRF token validation on all state-changing requests, including GET requests, through custom code or middleware. 6) Regularly check for official patches or updates from Lime Survey and apply them promptly once released. 7) Consider implementing multi-factor authentication (MFA) to reduce the impact of compromised sessions. 8) Conduct security assessments and penetration tests to verify the effectiveness of mitigations. These measures go beyond generic advice by focusing on compensating controls and proactive detection until an official patch is available.
Description
Lime Survey <= 6.5.12 is vulnerable to Cross Site Request Forgery (CSRF). The YII_CSRF_TOKEN is only checked when passed in the body of POST requests, but the same check isn't performed in the equivalent GET requests.