That’s putting it nicely. What’s happened is you’re showing users the wrong way to do something without it being explicitly clear to them. Then we wonder why people write crap code...
My view is NEVER simplify an example to the point it becomes a security or performance hazard.
What this tells me now is that this projects examples are not useable, their agenda is to make things appear easy when in fact concrete examples may not be.
There are also frameworks that do the sanitization for you (e.g. Rails IIRC), and novice developers coming from those certainly might not be aware.
And 'good' needs to be put in context: e.g. a 'good' hardware or kernel engineer who never wrote front-end stuff may legitimately be unaware of the need to defend against SQL injection unless its written somewhere.
If they're as 'good' as you're expecting they would probably not even require a getting started tutorial...
Anyway, this is something I see in many tutorials and its somewhat unfair to single out Lucee. I just wish tutorial writers would put effort into real-world examples more often.
SELECT * FROM #strDatabasePrefix#_courses WHERE intCourseID = <cfqueryparam value = #intCourseID# CFSQLType = "CF_SQL_INTEGER">
You would also want to protect your input variables so that you only get what you're expecting.
There's also a free service called HackMyCF that lets you check your server after you've hardened it with the guide that comes with both Lucee and Adobe CF.
https://foundeo.com/hack-my-cf/