Blog entries like that are frustrating - seems to be a user issue with the reviewer. We have included protection for Timthumb and other specific vulnerabilities via Wordfence scanning. So if you have the vulnerability you'll get a critical alert. This is more effective than, say, using an .htaccess rule to try to block the vulnerability from being exploited but leaving the vulnerability in place - we get the user to focus on the root cause of the issue and fix that.
Occasionally we will provide real-time patching of an issue via auto-updates. For example yesterday's release protects against the Slider Revolution issue even if you haven't upgraded yet. In this case, even though we'd like the user to deal with the root-cause and upgrade their version of Slider Revolution, the amount of PR around the issue creates enough risk that we rolled out additional protection until our customers can upgrade that plugin.
@perezbox Lets try to keep the marketing links to a minimum. We have many other high-profile competitors and partners on this forum making a valuable technical and support contribution and we welcome relevant contributions from you folks too, but lets keep it focused on supporting the community and on this forum specifically, providing customer support for Wordfence.
Regards,
Mark Maunder - Wordfence Founder.