Skip to content
Fencer Intel
medium 5.4

CVE-2019-16172 json

Cross-site Scripting in LimeSurvey

published 7y ago modified last mo. also GHSA-fr47-r224-c36m , EUVD-2022-3823

cvss
5.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.6%
EPSS 4.6% chance of exploitation in 30 days, percentile 91%
public exploits
1
Exploit-DB

Summary

LimeSurvey before v3.17.14 allows stored XSS for escalating privileges from a low-privileged account to, for example, SuperAdmin. The attack uses a survey group in which the title contains JavaScript that is mishandled upon group deletion.

Patch / fix

  • packagist limesurvey/limesurvey 3.17.14
  • limesurvey limesurvey 3.17.4

Is CVE-2019-16172 in your dependencies? 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

Timeline

  1. Published
  2. First public exploit (EDB-47386)

Exploit prediction

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

Exploits and checks

  • EDB-47386 LimeSurvey 3.17.13 - Cross-Site Scripting webapps, 2019-09-13
  • seclists.org http://seclists.org/fulldisclosure/2019/Sep/22 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/154479/LimeSurvey-3.17.13-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org https://seclists.org/bugtraq/2019/Sep/27 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist limesurvey/limesurvey
<3.17.14
3.17.14

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

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.