Limesurvey before 3.17.14 does not enforce SSL/TLS usage in the default configuration.

published 2019-09-09 7y ago modified 2026-06-17 4mo ago also EUVD-2019-6996

cvss: 5.3; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 0; none known

Patch / fix

fixed in 1 links 1

limesurvey limesurvey 3.17.14

github.com/LimeSurvey/LimeSurvey@5870fd1 commit

Is CVE-2019-16179 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness

CWE-295 Improper Certificate Validation

References

github.com /LimeSurvey/LimeSurvey/commit/5870fd1037058bc4e43cccf893b576c72293371e#diff-d539f3f8185667ee48db78e1bf65a3b4R4
patch, release-notes, third-party-advisory
limesurvey.org /limesurvey-updates/2188-limesurvey-3-17-14-build-190902-released
release-notes, vendor-advisory

Sources

CVE List CVE-2019-16179
NVD CVE-2019-16179

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.