Xojo's Handling of Security Vulnerabilities – A Serious Concern

Ouch:

https://forum.xojo.com/t/xojos-handling-of-security-vulnerabilities-a-serious-concern/89081

It is a long time known. XoJo isn’t secure and there is much more behind. Checking more than 20 Projects non was cyber secure. Not one project. XoJo Web IS definitely a big problem. But be careful. Nobody has done a lab check of Buoi or ObJo until now. That should be done one day by a third party. Only then you may know if it is secure. We had many compilers in our cyber labs to check. And many of them failed brutally. So who knows. XoJo has done it’s job. Not good. More bad. Let’s the future show if the competitors are ALSO doing their jobs better.

A third-party audit would help, but “20 projects, none secure” mixes framework defects with application-level issues. Xojo Web apps can be insecure because of session handling, input validation, authentication or deployment configuration, not only because the compiler/runtime is flawed. Without a defined threat model and reproducible findings, it is hard to compare Xojo with other toolchains. I would separate known vulnerability handling and disclosure from whether typical apps built with the tool are secure. Both matter, but they need different evidence.

I think “vulnability” and “security” have gotten a whole new meaning these last few years. Last week I read somewhere that with the help of AI a group discovered 942 vulnerabilities in Linux. Not the most shoddy product if I recall… What is the meaning of “secure” these days if a two year old toddler can hack the best protected products out there with the help of AI agents?