Here are some sample relevant links from a quick research on LimeSurvey and code injection:

• https://snyk.io/vuln/SNYK-PHP-LIMESURVEYLIMESURVEY-1074897
• https://bugs.limesurvey.org/view.php?id=6543
• https://bugs.limesurvey.org/view.php?id=6548
• https://bugs.limesurvey.org/view.php?id=15680
• (the official bug tracker have many more report like the three later items)

I didn't go in deep details, nor width spectrum but a high level overview seem to indicate that LimeSurvey do have code injection vulnerabilities points (XSS, SQL…) appearing in its code base here and there from time to time. That's not great, but not unusual in software industry and reveals more an improvable development/review/test process than a total lake of concern for the subject of security. On the contrary, the maintainers seem to take the reported bugs in considerations and seem to fix them (stats on median time to fix a security bug would be nice, but would require more time than I had to throw at it for now). The official bug tracker also have an option to pay for treating a bug, which seems to indicate a rather mature professional environment to back specific demands.

I didn't found any relevant reference about a report opened by the WMF it in the bug tracker (looking for terms like Wikipedia, Wikimedia and WMF). So it would be good if Tim Starling could give us more feedback on that point, as according to Philippe Beaudette it's the person who found the vulnerabilities and stashed the tool out of the Wikimedia software stack for understable security reasons. Feel free to ping them here if you know they have some account on Phabricator.

@tstarling and @Philippe are the tags you were looking for, just FYI.

Update. Italian Linux Society requested a price quotation to a cybersecurity company and there is consensus to carry out an initial security auditing soon.

understand what kind of security auditing has already been done on LimeSurvey by Wikimedia Foundation

Uhm. Apologies for the ping @Elitre but do you know someone who could tell us something about this point? I was not able to find any related information from the wikimedia-l mailing list. Thank you dear :)

Update. In two weeks the cybersecurity company commissioned by Italian Linux Society will begin their auditing on LimeSurvey CE.

Small digression. Talking about our preferences on their level of invasiveness.. the answer was more or less...

Take your biggest catapult and PULL - THAT - TRIGGER.

Did we have fun saying it? Yup.

This is in progress on the latest version of LimeSurvey CE right now.

In T275574#7080066, @valerio.bozzolan wrote:

understand what kind of security auditing has already been done on LimeSurvey by Wikimedia Foundation

Uhm. Apologies for the ping @Elitre but do you know someone who could tell us something about this point? I was not able to find any related information from the wikimedia-l mailing list. Thank you dear :)

Sorry, per my profile, pings on Phab aren't the most reliable way to reach out to me. I recommend you contact @LMixter .

@valerio.bozzolan Was this audit completed and, if so, were its findings published anywhere?

https://wikimediafoundation.limesurvey.net/

https://meta.wikimedia.org/wiki/LimeSurvey

Since it's provided as a service, security management is in charge of LimeSurvey GmbH itself.

BTW yep, the first round on the community edition was completed. With Italian Linux Society we need some time to remove some personal data and obtain consent for publication under a free license before being able to share it in the best way.

Anyway the report does not contain anything particularly outrageous: if you install LimeSurvey CE, the general recommendation is to check best practices about security headers and stay up to date.

I'll update soon.

Fantastic news, thank you Valerio!