Apenas 3 dias após o lançamento do WordPress 4.2, um pesquisador de segurança encontrou uma vulnerabilidade XSS de dia zero que afeta o WordPress 4.2, 4.1.2, 4.1.1, 4.1.3 e 3.9.3. Isso permite que um invasor injete JavaScript nos comentários e invada seu site. A equipe do WordPress respondeu rapidamente e corrigiu o problema de segurança no WordPress 4.2.1, e recomendamos enfaticamente que você atualize seus sites imediatamente.
Jouko Pynnönen, um pesquisador de segurança da Klikki Oy, que relatou o problema, descreveu-o como:
Se acionado por um administrador conectado, nas configurações padrão, o invasor pode aproveitar a vulnerabilidade para executar códigos arbitrários no servidor por meio dos editores de plug-ins e temas.
Como alternativa, o invasor pode alterar a senha do administrador, criar novas contas de administrador ou fazer qualquer outra coisa que o administrador conectado no momento possa fazer no sistema de destino.
Essa vulnerabilidade específica é semelhante à relatada por Cedric Van Bockhaven, que foi corrigida na versão de segurança do WordPress 4.1.2.
Infelizmente, eles não usaram a divulgação de segurança adequada e, em vez disso, publicaram a exploração publicamente em seu site. Isso significa que aqueles que não atualizarem seus sites correrão sérios riscos.
Atualização: Soubemos que eles tentaram entrar em contato com a equipe de segurança do WordPress, mas não obtiveram uma resposta em tempo hábil.
Se você não desativou as atualizações automáticas, seu site será atualizado automaticamente.
Mais uma vez, recomendamos enfaticamente que você atualize seu site para o WordPress 4.2.1. Certifique-se de fazer backup de seu site antes de atualizar.
Syed Balkhi says
Hey WPBeginner readers,
Did you know you can win exciting prizes by commenting on WPBeginner?
Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
You can get more details about the contest from here.
Start sharing your thoughts below to stand a chance to win!
Rajnish Tyagi says
hi there,
my site was 2 times in last week, i am using aws server, for database i am using RDS, but today my database was crashed it take 2 hours for recover, i am using the latest version of wprdress 4.2.2
please advice me some good security tips
Thanks
Rajnish
Paul says
Thanks for the post. I’ll update my sites immediately!
Mike says
If you have Akismet running there is a good chance that the comments will get flagged as spam so do not check your spam queue.
Bernhard says
Please take a look at http://klikki.fi/adv/wordpress2.html where it is clearly explained how they tried contacting wordpress.com and received no reply SINCE NOVEMBER 2014 (Confirmed vulnerable: WordPress 4.2, 4.1.2, 4.1.1, 3.9.3.):
“WordPress has refused all communication attempts about our ongoing security vulnerability cases since November 2014. We have tried to reach them by email, via the national authority (CERT-FI), and via HackerOne. No answer of any kind has been received since November 20, 2014. According to our knowledge, their security response team have also refused to respond to the Finnish communications regulatory authority who has tried to coordinate resolving the issues we have reported, and to staff of HackerOne, which has tried to clarify the status our open bug tickets.”
If that is correct, disclosing the issue was the only responsible thing to do, and sites are vulnerable not because of the disclosure, but because of the failure on the part of WordPress to address this issue for almost 6 Months.
I understand that security is a complex issue, but please get your facts straight.
WPBeginner Support says
Our sincerest apologies. We have updated the article.
Administrador
Bilal Bin Amar says
but after the update, my CMS(wordpress) and my Site have became very slow, under the CMS when i click in the added a plugin this is giving error
William Charles says
I was auto updated and now it’s asking me to update my database, when I update my data base I get the following error: Catchable fatal error: Object of class WP_Error could not be converted to string in /home/doctorof/public_html/wp-admin/includes/upgrade.php on line 1459
Any thoughts on how to fix it? Tried the usual methods (turning off plugins, default theme etc).
Editorial Staff says
Please get in touch with your hosting provider. This may be happening due to a database corrupt table. We had it happened with our site List25, and our host was able to fix it right away.
Administrador
kunwar says
Just visit your admin login page /wp-admin and then press the update database button, this should fix the issue.
pmisun says
After the auto update applied it totally messed up our instances and we got no server responses. Investigating for 6 hours now, with no positive results. Server is fine, ip providers / isps are fine…
raja babu says
i want to know how can i secure my site , how can i stop auto update of site??? please help me
WPBeginner Support says
It is highly recommended that you update your WordPress site as soon as there is a new update is available. Not doing so makes your site vulnerable. However, if for some reason you want to update manually, then you can disable automatic updates in WordPress
Administrador
Elaine Maul says
Thank you for the alert! Although I have automatic updates set, it hadn’t got round to doing it yet for some reason, so I have actioned it myself
Thank you
ha manh bui says
How can i know if my site http://homelytips.com/ is effecte, it just auto update itself to 4.1.4
Editorial Staff says
The auto update is done by the WordPress team if you didn’t disable them.
4.1.4 also fixes the issue.
Administrador