LimeSurvey Community Edition 7.7.0 - Stored XSS in Central Participants blocklist control
- Exploited
- No known exploitation
- Fix
- Fixed in 7.9.0 or later
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 7.9.0 or later.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.28% · 20th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
LimeSurvey Community Edition contains a stored cross-site scripting flaw in its Central Participants Database blocklist control. An attacker with a low-privilege logged-in account can remotely import a crafted participant ID containing HTML, which runs in the browser of a CPDB editor who opens the participant list, letting the attacker access session-exposed data and act with that editor's permissions.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
LimeSurvey Community Edition 7.7.0 contains a stored cross-site scripting vulnerability in the Central Participants Database blocklist control. An authenticated user with only global participantpanel:import permission can import a CSV participant_id containing HTML. The import flow persists that value without model validation. When a CPDB editor opens the participant list, LimeSurvey derives ButtonGroupWidget id and name attributes from participant_id and inserts them without HTML encoding, causing attacker-controlled markup to execute in the victim's authenticated LimeSurvey origin. Exploitation can access session-exposed data and issue same-origin requests with the victim's effective permissions.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 7.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Upgrade to a fixed version: 7.9.0 or later.
Workaround: Restrict CPDB Import and Update permissions and remove suspicious participant IDs until upgrade completion.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-115640 (LimeSurvey Community Edition 7.7.0 - Stored XSS in Central Participants blocklist control), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-115640 (entry last updated 2026-11-10): Affected: - LimeSurvey LimeSurvey Community Edition: from 3.0.0, through 7.7.0 Fixed versions: 7.9.0 or later. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, a user action. Workaround: Restrict CPDB Import and Update permissions and remove suspicious participant IDs until upgrade completion. (source: https://www.cve.org/CVERecord?id=CVE-2026-115640) CISA KEV: CVE-2026-115640 is not listed as of cve.now's last read. This KEV status is for CVE-2026-115640 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/LimeSurvey/LimeSurvey/commit/4cd281828422abf94468052016eba8897d5ec9aa - https://fluidattacks.com/es/advisories/angel - https://github.com/LimeSurvey/LimeSurvey/ - https://github.com/LimeSurvey/LimeSurvey/releases/tag/7.9.0+261029 - https://www.cve.org/CVERecord?id=CVE-2026-115640 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-115640 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-115640.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- LimeSurvey LimeSurvey Community Edition
From 3.0.0 · through 7.7.0
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115640
Is CVE-2026-115640 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-115640?
LimeSurvey Community Edition: from 3.0.0 through 7.7.0.Source: cve.now feed data
How do I fix CVE-2026-115640?
Upgrade to LimeSurvey Community Edition 7.9.0 or later. Until the upgrade is complete, restrict the CPDB Import and Update permissions and remove suspicious participant IDs.Source: cve.org