CVE
LimeSurvey unauthenticated SQL injection in public statistics
Affects LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813 when the database is MySQL or MariaDB. Fixed in 6.17.16+260814 and 7.0.10+260813.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 6.17.16+260814, 7.0.10+260813
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.17.16+260814, 7.0.10+260813.
- 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
- 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? →
- 25/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? →
- Unclear
- 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: partial
Summary
LimeSurvey is affected through its public statistics page, where a flaw in how POST parameter names are handled lets an attacker run SQL injection remotely, without logging in. An attacker could use blind techniques to read administrator password hashes and survey responses on MySQL or MariaDB databases.
Original description
LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813 contains an unauthenticated SQL injection vulnerability in the public statistics page via POST parameter names. Attackers can submit backtick-containing parameter names to buildSelects() and use blind techniques to read administrator password hashes and survey responses on MySQL or MariaDB.
Who should check
Teams running LimeSurvey 6.x before 6.17.16+260814 or 7.x before 7.0.10+260813 with MySQL or MariaDB, including the public statistics page.
“LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813”
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.17.16+260814, 7.0.10+260813.
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-129853 (LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813 Unauthenticated SQL Injection via Public Statistics), 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-129853 (entry last updated 2026-11-16):
Affected:
- LimeSurvey LimeSurvey: fixed in 6.17.16+260814; from 7.0.0, fixed in 7.0.10+260813
Fixed versions: 6.17.16+260814, 7.0.10+260813.
Conditions (all must be true for the bug to be hit):
- Affects LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813. (source: https://www.vulncheck.com/advisories/limesurvey-before-6.17.16-260814-and-7-x-before-7.0.10-260813-unauthenticated-sql-injection-via-public-statistics)
- Requires MySQL or MariaDB as the database. (source: https://www.vulncheck.com/advisories/limesurvey-before-6.17.16-260814-and-7-x-before-7.0.10-260813-unauthenticated-sql-injection-via-public-statistics)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129853 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129853 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/pull/5225
- https://github.com/LimeSurvey/LimeSurvey/commit/a628daa5dc30cb40567dcfb541a92fd67beaeb65
- https://github.com/LimeSurvey/LimeSurvey/commit/6df34368fc83ef9357c86da6163d6b1605beb6da
- https://github.com/LimeSurvey/LimeSurvey/blob/83896f131ad3c66513a7fae851b6eabe846c845c/application/helpers/userstatistics_helper.php#L325-L373
- https://www.vulncheck.com/advisories/limesurvey-before-6.17.16-260814-and-7-x-before-7.0.10-260813-unauthenticated-sql-injection-via-public-statistics
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-129853
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129853"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- LimeSurvey LimeSurvey
fixed in 6.17.16+260814; From 7.0.0 · fixed in 7.0.10+260813
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Patch
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129853
Is CVE-2026-129853 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
What does this mean?
An unauthenticated SQL injection flaw in LimeSurvey's public statistics feature lets an outside visitor send crafted input that alters database queries. Using blind techniques, the flaw can read administrator password hashes and survey responses.Source: vulncheck.com
Which versions are affected by CVE-2026-129853?
LimeSurvey: before 6.17.16+260814; from 7.0.0 before 7.0.10+260813.Source: cve.now feed data
Am I affected, and how do I check?
Affected are LimeSurvey versions before 6.17.16+260814 and 7.x versions before 7.0.10+260813, and the issue applies only when the database is MySQL or MariaDB. To check, look at the LimeSurvey version in the administration panel and the database type in the configuration file.Source: vulncheck.com
How do I fix CVE-2026-129853?
Upgrade to LimeSurvey 6.17.16+260814 or 7.0.10+260813, whichever matches your release line. The advisory names no separate patch identifiers or workaround.Source: vulncheck.com