Skip to main content
VulnerabilityPublished

CVE-2024-42902: LimeSurvey · Code Injection

Affects LimeSurveySource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Affected software

ProductAffectedFixed in
GitHublimesurvey/LimeSurveypkg:github/limesurvey/LimeSurveyOther threatsAffected
  • <=6.6.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade LimeSurvey to the latest version once an official patch addressing CVE-2024-42902 is released.
  2. Until patches are available, restrict access to the js_localize.php endpoint via web application firewalls (WAFs) or network access controls, limiting it to trusted IP addresses or internal networks only.
  3. Implement input validation and sanitization at the web server or application firewall level to block suspicious payloads targeting the 'lng' parameter.
  4. Monitor web server logs for unusual or repeated requests to js_localize.php containing suspicious or malformed 'lng' parameters.
  5. Employ runtime application self-protection (RASP) tools if available to detect and block code injection attempts in real time.
  6. Conduct thorough security audits and penetration testing focusing on LimeSurvey installations to identify any signs of compromise or exploitation attempts.
  7. Educate system administrators and developers about this vulnerability to ensure prompt response and remediation.
  8. Consider isolating LimeSurvey instances in segmented network zones to limit lateral movement in case of compromise.

Description

An issue in the js_localize.php function of LimeSurvey v6.6.2 and before allows attackers to execute arbitrary code via injecting a crafted payload into the lng parameter of the js_localize.php function

References

Community reviews

Loading reviews…