Skip to main content
VulnerabilityPublished

CVE-2026-116645: LimeSurvey Community Edition 7.8.0 contains an SQL injection vulnerability in the survey-archive

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116645· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 11 Nov 2026, 04:36 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Fluid Attacks)CVSS 4.07.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
LimeSurveyLimeSurvey Community EditionAffected
  • =7.8.0
Fixed in–
GitHubLimeSurvey Community Editionpkg:github/LimeSurvey Community EditionOther threatsAffected
  • =7.8.0
Fixed in–

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

AI-suggested

Until a fix is available, restrict global surveys.create permissions to trusted users only and monitor for any unusual activity related to survey imports and exports.

Description

LimeSurvey Community Edition 7.8.0 has an SQL injection vulnerability in the survey-archive participant import and SPSS-response export workflow. An authenticated user with global surveys.create permission can craft a .lsa archive that leads to execution of attacker-controlled SQL commands when exporting responses from the imported survey. This occurs because attribute names containing parentheses are treated as SQL expressions rather than quoted identifiers.

References

Community reviews

Loading reviews…