New WordPress vuln emerges
W3 Total Cache has faulty defaults
Sorry to spoil the day for any sysadmins that thought today would be a slow day, but a security researcher has announced a serious vulnerability in the default configuration of a popular WordPress plugin.
W3 Total Cache, which boasts high-traffic sites like Mashable and Lockergnome among its users, has serious vulnerabilities, according to this post on the Full Disclosure list.
The default setup – that is, when users simply choose “add plugin” from the WordPress catalogue – left cache directory listings enabled, according to poster Jason Donenfield.
This, he said, allows database cache keys to be downloaded on vulnerable installations – and that could expose password hashes. “A simple google search of "inurl:wp-content/plugins/w3tc/dbcache" and maybe some other magic reveals this wasn't just an issue for me”, he writes.
Donenfield later amended the search term to “inurl:wp-content/w3tc”.
“Even with directory listings off,” he continues, “cache files are by default publicly downloadable, and the key values / file name of the database cache items are easily predictable.”
Donenfield says the developer of the plug-in intends to release a fix “soon”. In the meantime, he notes that “deny from all” should be set in the .htaccess file. ®
So... not a wordpress vulnerability but a plugin vulnerability. That's like saying "Massive Windows vulnerability!" in the Logitech USB speaker software!
Re: Windows is bad, so is PHP
Ok Eadon ,we get it. You need to mention Windows in every article, even if in no way is it related (.htaccess is used more Linux boxes than IIS servers, but let's ignore that). But you know what, I reckon your a closet MS lover, bit like those homophobic MP's that turn up in the gutter press with a ball gag in their mouth and a butt plug rammed where the sun don't shine.
Admit, you secretly luurve MS....go on, we won't mock you...feel the love.
MS and Eadon sitting in a tree,,,,,
i'll prepare for the downvotes
I've upvoted you, just to confuse matters :)
BTW, quite a few people don't have command line access to their service, so the .htaccess method is sometimes the only reliable control they have, barring CHMOD features in their FTP client.