Fixed in version 5.2.4 which was released this morning. Our customers are auto-updated to the new version.
Regards, Mark. On Sun, Sep 14, 2014 at 11:11 PM, Voxel@Night < [email protected]> wrote: > > > Wordfence v5.2.3 suffers from multiple vulnerabilities. > Stored XSS in IPTraf.php resulting from failing to sanitize > $_SERVER['REQUEST_URI'] > Stored XSS in cached pages resulting from failing to sanitize > $_SERVER['HTTP_HOST'] <-- Yep, you can put javascript in the host header > Insufficient Logging - One can trivially avoid having your requests logged > because of some crappy code designed to filter out some types of requests > Throttle bypass - Unlogged requests won't trigger automatic throttling and > banning > Revolution Slider exploit protection bypass - people seriously need to > learn how $_REQUEST works. > Also, if you have a few bucks to buy a domain name, you can make the > plugin tell the admin that your IP belongs to google when they try to ban > you. > > Details can be found here: > https://vexatioustendencies.com/wordfence-v5-2-3-2-stored-xss-insufficient-logging-throttle-bypass-exploit-detection-bypass/ > > -Voxel@Night > > > _______________________________________________ > Sent through the Full Disclosure mailing list > http://nmap.org/mailman/listinfo/fulldisclosure > Web Archives & RSS: http://seclists.org/fulldisclosure/ > _______________________________________________ Sent through the Full Disclosure mailing list http://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: http://seclists.org/fulldisclosure/
