Jan 15, 2016
How to Speed Up Your WordPress Website As everybody knows speed of the site matters a lot in the today’s world. Speed is a quality that all the websites or services should maintain, and thus WordPress is not an exception.
Loading...
seen from Germany
seen from United States
seen from Australia
seen from South Africa
seen from United States
seen from United States
seen from Czechia
seen from United Kingdom
seen from Malaysia
seen from United States
seen from Germany
seen from United States
seen from United Kingdom
seen from China
seen from United Kingdom
seen from Brazil
seen from Germany
seen from China
seen from United States
seen from United States
How to Speed Up Your WordPress Website As everybody knows speed of the site matters a lot in the today’s world. Speed is a quality that all the websites or services should maintain, and thus WordPress is not an exception.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
W3 Total Cache #infosec #Security Update 0.9.4.1
W3 Total Cache Security Update — update with XSS attack
December 12, 2014 by Planet Zuda
W3 Total Cache 0.9.4.1 is a #wordpress plugin security update. If you aren’t aware what W3 Total Cache is, it is a caching plugin for WordPress. Caching helps speed up your sites. One of the issues which has been made public by another researcher is broken security in the WordPress nonces. Most plugins accidentally create numbers used once, also known as  nonces that are insecure, because of the way WordPress core works. If you use a function called wp_create_nonce(), it makes a broken nonce unless you also use the function wp_verify_nonce to try and make sure the nonce is valid. This is what was discovered and written about on WPScan.
Unfortunately, there was a misunderstanding that caused a delay in  the release. W3 Total Cache made the best patch possible, so this problem will not occur again in their plugin. Their design of stopping the issue was creative and did fix the issue.  It would be best if researchers followed nahamsec.com’s advice on how to treat companies even if you didn’t use to act the way listed, you should try and change your behavior.
The changelog notes an xss attack vector via html comments. This is an issue when you have error logging turned on and php errors occur. When an error occurs someone can tamper with what is being sent across and execute cross site scripting into the error log on the admin side. So, to recap if you have error logging turned on, which isn’t on by default an attacker can inject cross site scripting into your admin panel.  W3 Total Cache created a patch in 0.9.4.1.  Multiple different patches were discussed with WordPress Security and Planet Zuda for this issue. If you have error logging turned off you are not vulnerable to this attack. WordPress security decided this attack isn’t as easy for most to use, since the xss would go to a file that does not use a normal extension, like php.
Can't get BackWPup to Authenticate with Dropbox ... read on SugarSync is cancelling their free plans so I've decided to move all my offsite backups over to Dropbox. But BackWPup wouldn't authenticate... it was driving me nuts. Turns out the fix is real simple... W3TC. #Wordpress  #Dropbox  #W3TC http://click-to-read-mo.re/p/4t1o
Let's install this plugin - OH SHIT
So I was trying to install W3 Total Cache on my blog, and something went horribly wrong. Couldn't disable or add any new plug-ins, especially not W3TC.
So I went undercover and removed it via FTP. Still nothing worked, and now I couldn't log into the Wordpress Dashboard. Dammit.
Did more research. Played with .htaccess files, still no dice.
Hey look, the error is on line 2 of such and such.php. Oh, this is simple to fix. Delete the empty white space. Cool. Yay! I don't get that error message anymore. Better check the front end of the site. Oh, hell. It's displaying the contents of my wp-config.php file, which is serious fucking business. Now I have to reintroduce the error to the first .php file so that wp-config isn't displayed to the world. This sucks. Been working on it for four hours now. Worse off than I was before. I could reinstall WordPress. That would blow. I could keep dicking around with this. I don't know PHP, I'm shooting from the hip in the dark here. Virtually zero chance I'll get it right. This blows so much.
What the hell am I supposed do now?