Maybe, but doesn't that require that the attacker can set ENV variables for the executed bash command? I'm sure it happens, but it seems unlikely to be a major concern for most dynamic sites?
(I'm not arguing against the notion that static sites can be more secure, just that the article is bad ;)
I don't know a lot about it but I do remember reading that if you are using bash to process CGI or bash is spawned by a process that is handling CGI then the env is augmented with variables containing the contents of the http headers sent back by the client - thus giving an attacker a way to add to the environemnt.
Again, I'm a bit sketchy on the details. We mitigated this on one server we have where it might have been an issue by simply disabling bash and sym linking sh to pdksh.
And, yeah, the article does seem a bit schizophrenic...
(I'm not arguing against the notion that static sites can be more secure, just that the article is bad ;)