CVE-2026-129853: LimeSurvey before 6.17.16+260814 and 7.x before 7.0.10+260813 Unauthenticated SQL Injection via Public Statistics
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- No fixed version is recorded, but the references include a patch (commit or PR) link.
Low priority for now. See the fix and affected versions sections below.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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.
- Published
- Nov 16, 2026
- Updated
- Nov 16, 2026
- EPSS
- —
- CWE
- CWE-89
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
LimeSurvey LimeSurvey
- before 6.17.16+260814affected
- 7.0.0 and later · before 7.0.10+260813affected
Same product
limesurvey: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11455LimeSurvey before 4.1.12+200324 contains a path traversal vulnerability in application/controllers/admin/LimeSurveyFileManager.php.68This week
- CVE-2019-9960The downloadZip function in application/controllers/admin/export.php in LimeSurvey through 3.16.1+190225 allows a relative path.60This week
- CVE-2007-3632Multiple PHP remote file inclusion vulnerabilities in LimeSurvey (aka PHPSurveyor) 1.49RC2 allow remote attackers to execute arbitrary PHP…45Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-91775Sep 23, 2026 · LimeSurvey Community Edition 7.0.14 - Reflected XSS through unescaped LSS survey-import warnings29Monitor
- ← EarlierCVE-2026-97685Sep 29, 2026 · LimeSurvey Community Edition 7.3.0 - Cross-survey object authorization bypass in REST survey patch operations28Monitor
- ← EarlierCVE-2026-102626Oct 2, 2026 · LimeSurvey Community Edition 7.4.0 - Stored XSS through the Date/Time date_min question attribute28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- JeongAhn Jangfinder
- Carsten Schmitzremediation developer
Not on record for this CVE: EPSS history · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
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/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
nvd-secondary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
- github.com/LimeSurvey/LimeSurvey/commit/6df34368fc83ef9357c86da6163d6b1605beb6da
- github.com/LimeSurvey/LimeSurvey/commit/a628daa5dc30cb40567dcfb541a92fd67beaeb65
- github.com/LimeSurvey/LimeSurvey/pull/5225
- www.vulncheck.com/advisories/limesurvey-before-6.17.16-260814-and-7-x-before-7.0.10-260813-unauthenticated-sql-injection-via-public-statistics
Vendor advisories and official records. Exploit/PoC links are deliberately left out.