GHSA-fr47-r224-c36m is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in limesurvey/limesurvey. 6 public exploit references exist, so weaponization risk is real. A fix is available for limesurvey/limesurvey — see the affected versions and patch details below.
Cross-site Scripting in LimeSurvey
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-fr47-r224-c36m by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
limesurvey/limesurveyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | limesurvey/limesurvey | all versions | 3.17.14composer require limesurvey/limesurvey:^3.17.14 |
Affected Products
limesurveylimesurveyResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
LimeSurvey 3.17.13 - Cross-Site Scripting
by SEC Consult · Sep 13, 2019
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for limesurvey/limesurvey, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update limesurvey/limesurvey to 3.17.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fr47-r224-c36m is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-fr47-r224-c36m in your dependencies?
Find it across Packagist, including transitive dependencies.