LIMESURVEY · CVE-2026-129853 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
LimeSurvey's public statistics page passes POST parameter names unsafely into a SQL query, so anyone on the internet can send crafted requests. An attacker can use blind SQL techniques to read administrator password hashes and survey responses on MySQL or MariaDB.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
LimeSurvey instances on the 6.x line before 6.17.16+260814 or the 7.x line before 7.0.10+260813 running on MySQL or MariaDB are exposed through the public statistics page. The sources do not say whether a default configuration exposes that page, so treat any internet-facing LimeSurvey as in scope until checked. Teams that run LimeSurvey only on a private network with no public statistics page can deprioritise it.
Not affected if postgresql-database, private-network-only
Who cares limesurvey, mariadb, mysql, php, self-hosted
6.17.16+260814 or later.7.0.10+260813 or later.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.