Skip to main content
VulnerabilityPublished

CVE-2026-63361: LimeSurvey Community Edition 7.0.5 contains an authenticated reflected cross-site scripting

Affects LimeSurveySource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.5 High.

Data as of 13 Nov 2026, 23:54 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 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 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHublimesurvey/LimeSurveypkg:github/limesurvey/LimeSurveyOther threatsAffected
  • =7.0.5
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 an official fix is available, users should consider limiting access to trusted authenticated users and monitor for suspicious activity related to the HTML editor popup endpoint. Avoid relying solely on blacklist sanitization and implement context-appropriate output encoding as a best practice once a fix is available.

Description

LimeSurvey Community Edition 7.0.5 contains an authenticated reflected cross-site scripting (XSS) vulnerability in the HTML editor popup endpoint. The vulnerability arises because the text and name query parameters are filtered by a blacklist sanitizer but then rendered without proper context-appropriate output encoding. This flaw allows an authenticated attacker to inject malicious scripts that could execute in the context of the affected application.

References

Community reviews

Loading reviews…