WordPress.org

Ready to get started?Download WordPress

WordPress 2.1.1 dangerous, Upgrade to 2.1.2

Posted March 2, 2007 by Matt Mullenweg. Filed under Releases.

Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.

Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened.

It was determined that a cracker had gained user-level access to one of the servers that powers wordpress.org, and had used that access to modify the download file. We have locked down that server for further forensics, but at this time it appears that the 2.1.1 download was the only thing touched by the attack. They modified two files in WP to include code that would allow for remote PHP execution.

This is the kind of thing you pray never happens, but it did and now we’re dealing with it as best we can. Although not all downloads of 2.1.1 were affected, we’re declaring the entire version dangerous and have released a new version 2.1.2 that includes minor updates and entirely verified files. We are also taking lots of measures to ensure something like this can’t happen again, not the least of which is minutely external verification of the download package so we’ll know immediately if something goes wrong for any reason.

Finally, we reset passwords for a number of users with SVN and other access, so you may need to reset your password on the forums before you can login again.

What You Can Do to Help

If your blog is running 2.1.1, please upgrade immediately and do a full overwrite of your old files, especially those in wp-includes. Check out your friends blogs and if any of them are running 2.1.1 drop them a note and, if you can, pitch in and help them with the upgrade.

If you are a web host or network administrator, block access to “theme.php” and “feed.php”, and any query string with “ix=” or “iz=” in it. If you’re a customer at a web host, you may want to send them a note to let them know about this release and the above information.

Thanks to Ryan, Barry, Donncha, Mark, Michael, and Dougal for working through the night to figure out and address this problem, and thanks to Ivan Fratric for reporting it in the first place.

Questions and Answers

Because of the highly unusual nature of this event and release, we’ve set up an email address 21securityfaq@wordpress.org that you can email questions to, and we’ll be updating this entry with more information throughout the day.

Is version 2.0 affected?

No downloads were altered except 2.1.1, so if you’ve downloaded any version of 2.0 you should be fine.

What if we update from SVN?

Nothing in the Subversion repository was touched, so if you upgrade and maintain your blog via SVN there is no chance you downloaded the corrupted release file.

837 Pings

RSS feed for comments on this post.

  1. [...] Wer gerade nichts zu tun hat, kann ja mal wieder sein WordPress updaten. [...]

    Pingback from Langeweile, anyone? » Missis Notizblock on March 2, 2007

  2. [...] has just announced that recent .zip and tar.gz download packages of WordPress contains an exploit. A cracker managed [...]

    Pingback from WordPress Security Exploit Announced - Version 2.1.2 available to download | Cormac Moylan on March 2, 2007

  3. [...] You can read the details of this update here. [...]

    Pingback from WordPress 2.1.2 Just Released : Refueled Dot Net on March 2, 2007

  4. [...] WordPress 官方的号召,尽量通知用 WordPress 的朋友:Wordpress 2.1.1 [...]

    Pingback from WP 2.1.1 危险,赶快升级! | 巧克力工厂 (Beta5) on March 2, 2007

  5. [...] please go and upgrade your blogs right now if you are using WordPress 2.1.1. As Matt outlines, a hacker managed to gain access to the Automattic server with the file downloads and modified core files. The entire 2.1.1 version has been declared [...]

    Pingback from EMERGENCY: WordPress 2.1.1 Hacked, Upgrade Released » Technology, Blogging and New Media on March 2, 2007

  6. [...] n’est pas moi qui le dit mais Matt de WordPress. N’hésitez pas, passez à WordPress 2.1.2 aujourd’hui. Pour ma part, je prévois passer à Drupal mais je ne sais pas trop quand je pourrai, alors entre [...]

    Pingback from IM2 | OQP » Autre jour, autre mise à jour on March 2, 2007

  7. [...] is from the WordPress development blog and worth noting if you run WordPress as your blog software: Long story short: If you downloaded [...]

    Pingback from Why Dont You Blog? : WordPress Security Problem on March 2, 2007

  8. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Just my luck!! at Jonesieblog on March 2, 2007

  9. [...] press release from WordPress came today: ” If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from important WordPress news at Daily.Phirebrush on March 2, 2007

  10. [...] Хакер получил доступ к главному серверу wordpressа, и поменял файлы последнего релиза, добавив туда backdoor, позволяющий исполнять на серверах с wordpress 2.1.1 произвольный php-код. [...]

    Pingback from Val Petruchek » Почему WordPress — гавно. Часть вторая. on March 2, 2007

  11. [...] You can read more on the dev blog: WordPress 2.1.1 dangerous, Upgrade to 2.1.2. [...]

    Pingback from CompuSkills Web Design Service » Blog Archive » WordPress Upgrade Needed on March 2, 2007

  12. WordPress 2.1.1 es peligroso. Upgrade!

    Si descargaste WordPress 2.1.1 hace 3-4 dias, los archivos pueden incluir un exploit de seguridad que ha sido añadido por un cracker, y debes actualizar todos los archivos a 2.1.2 inmediatamente.

    Trackback from meneame.net on March 2, 2007

  13. [...] Malicious Destruction And other shiny objects in the world. http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from http://wordpress.org/development/2007/03/upgrade-212/ on March 2, 2007

  14. [...] wie der schadhafte Code aufgefallen und vor allem in den Release integiert werden konnte ist im Development Blog zu finden. Die Entwickler von WordPress geloben aber Besserung, so dass solch ein Vorfall sich [...]

    Pingback from Gefährliche Sicherheitslücke in WordPress 2.1.1 | Bloganbieter.de Blog on March 2, 2007

  15. WordPress Update 2.1.2

    Trackback from functional bytes blog on March 2, 2007

  16. [...] Actualización: Todo el que use WP 2.1.1 que actualice inmediatamente a la nueva versión 2.1.2 . Se ha detectado un importante fallo de seguridad inducido por un hacker. [...]

    Pingback from Actualización Efecte-d. WordPress, plugins, temas, hacks … at Efecte-D on March 2, 2007

  17. [...] wordpress inizi 2.1.2 versiyonuna çýkarmanýz. Yoksa bu açýktan etkilenebilirsiniz Ayrýntýlý bilgi WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Buradan indirebilirsiniz. http://wordpress.org/latest.zip __________________ BEN MEVLANA DEÐÝLÝM [...]

    Pingback from WordPress 2.1.1 'de Büyük Açýk Acilen Güncelleyin - Webmaster Zone on March 2, 2007

  18. [...] know that WP 2.1.1 — the version this blog was running up until a few minutes ago — was apparently tainted. Sheesh! Say, Matt, since you WordPress folk are fixing things today how about we make TinyMCE work [...]

    Pingback from WordPress 2.1.1 tainted » Ryan Block on March 2, 2007

  19. [...] descritto qui un cracker ha aggiunto un security exploit modificando i file di WordPress 2.1.1, è indispensabile [...]

    Pingback from » Gravissimo problema di sicurezza in WordPress 2.1.1 - Parole in rete on March 2, 2007

  20. [...] For further details see the WordPress Blog [...]

    Pingback from WordPress 2.1.1 Users - Important Update on March 2, 2007

  21. [...] avete aggiornato negli ultimi 3 o 4 giorni. C’è stata un’intrusione in un server di WordPress.org, ed un cracker ha uploadato una versione modificata dei files di installazione. Basta scaricare la [...]

    Pingback from Andrea Beggi » Aggiornate subito WordPress! on March 2, 2007

  22. [...] sure you download the update right away and patch your installation. If you have any information on how this happened, WordPress [...]

    Pingback from Upgrade Immediately to WordPress 2.1.2! | Stephen Fung DOT NET on March 2, 2007

  23. [...] caught wind of this about 20 minutes ago but wanted to upgrade my blog before I posted about it. So, now my WordPress [...]

    Pingback from Cocoa Crusty » Blog Archive » WordPress Download 2.1.1 Compromised on March 2, 2007

  24. [...] include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 [...]

    Pingback from Dietro è la casa, davanti a noi il mondo... - di Matteo Villani » Blog Archive » WordPress 2.1.2 on March 2, 2007

  25. [...] in the 2.1.1 archive were cracked and contains malicious code. If you are running WordPress, please download that upgrade now and patch your installations. If you downloaded 2.1.1, trash it right away and do not use it. [...]

    Pingback from WordPress Users: Update to 2.1.2 Immediately » MEGATechNews :: Mega Techie Goodness For the Masses on March 2, 2007

  26. [...] [Wordpress Blog] [...]

    Pingback from TasSense » ***URGENT*** : Upgrade to WordPress 2.1.2 on March 2, 2007

  27. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from geschonneck.com » WordPress 2.1.1 with backdoor on March 2, 2007

  28. [...] than an hour old: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include… Upgrade on this site in [...]

    Pingback from This Just In: WordPress 2.1.1 dangerous! at raincontreras.com on March 2, 2007

  29. [...] cow badness: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Trackback Friday, March 2, 2007 [...]

    Pingback from Holy cow badness: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 - Justinsomnia on March 2, 2007

  30. [...] WordPress crew have announced that the WordPress 2.1.1 download got cracked by an unnamed attacker who injected some code that would allow remote code execution. I’m glad I [...]

    Pingback from Yikes! WordPress Hacked! » Yabfog on March 2, 2007

  31. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from WordPress 2.1.2发布 at LIVE on March 2, 2007

  32. [...] you upgraded to 2.1.1 recently immediately go here site and download [...]

    Pingback from [This Savage Art] » WordPress 2.1.1 Security Risk on March 2, 2007

  33. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from WordPress 2.1.2! ÂÀÆÅÍ ÚÏÄÅÉÒ! | áëîãúò íà Àòàíàñ ßíåâ on March 2, 2007

  34. [...] Anyone who previously upgraded to WordPress 2.1.1 should upgrade to WordPress 2.1.2 immediately. Here’s more info. This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from Laughing Squid » Alert, Upgrade To WordPress 2.1.2 on March 2, 2007

  35. [...] an hour ago WordPress released news that part of their internal structure has been penetrated by a hacker whom embedded a possibility [...]

    Pingback from In Fire We Trust » Blog Archive » Hack in WordPress on March 2, 2007

  36. [...] poco más de una hora Matt (desarrollador de WordPress) ha informado de código malicioso en WordPress 2.1.1. Recomienda actualizar URGENTEMENTE a la nueva versión [...]

    Pingback from Punto y seguido… » Blog Archive » ¡Actualización URGENTE a WordPress 2.1.2! on March 2, 2007

  37. [...] seems that WordPress 2.1.1 contained malicious code due to a compromise of one of WordPress’s download servers. I just finished upgrading to [...]

    Pingback from Small Eyes, Big Mouth · Another Another Upgrade on March 2, 2007

  38. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 (WordPress.org) [...]

    Pingback from apakuni.com » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 2, 2007

  39. [...] Read the full announcement on wordpress.org. [...]

    Pingback from Upgrade to WordPress 2.1.2 now « moeffju.net on March 2, 2007

  40. WordPress Server gehackt. Dangerous Update 2.1.2. verfügbar

    Autsch. Jetzt werden die WordPress Updates schon mit dangerous deklariert. Was hat es damit auf sich?
    Offensichtlich ist es einem Hacker, der scheinbar gerade nichts Besseres zu tun hatte, gelungen, sich Zugriff zum WordPress-Server zu verschaffen und …

    Trackback from fob marketing on March 2, 2007

  41. [...] seems that the WordPress development team inadvertently allowed a hacker into their midst and he/she included some unauthorized (and potentially dangerous) [...]

    Pingback from Site maintenance - Phase 3 - The Space Elevator Blog on March 2, 2007

  42. Peligro! WordPress 2.1.1 crackeado

    Desde la web de WordPress nos informan que la versión 2.11 fue crackeado desde hace unos 3, 4 días por un cracker quien agrego un Exploit dentro de los archivos.

    Trackback from Fresqui.com on March 2, 2007

  43. [...] ダウンロード WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2より [...]

    Pingback from WordPress 2.1.1は危険です、2.1.2にアップグレードしてください on March 2, 2007

  44. [...] Blog de WordPress [...]

    Pingback from Blog no oficial de DreamHost » Archivo » Actualización WordPress y MediaWiki on March 2, 2007

  45. [...] security announcement for WordPress users who have updated to version 2.1.1: the download file for 2.1.1 was apparently cracked to include a security exploit. If your WordPress site is running 2.1.1 and you obtained that version from any source other than [...]

    Pingback from Sliding Constant » WordPress 2.1.1 has dangerous hole on March 2, 2007

  46. [...] from here: WordPress 2.1.1 Dangerous, Upgrade Download 2.1.2 here: WordPress » [...]

    Pingback from Joiz and the Angels Lair » Warning! For My WP Blogging Friends! on March 2, 2007

  47. [...] at night when I had logged to my blog I saw the news from WordPress.org that a hacker attacked WordPress server and published modified version of original code. Well, no [...]

    Pingback from 2000 Bloggers - » ATTENTION: WordPress 2.1.1 dangerous! on March 2, 2007

  48. [...] Aggiornate subito WordPress!: Se avete aggiornato negli ultimi 3 o 4 giorni. C’è stata un’intrusione in un server di WordPress.org intrusione in un server di WordPress.org, ed un cracker ha uploadato una versione modificata dei [...]

    Pingback from FreeUser.Org » WordPress 2.1.1 hacked - Aggiornate on March 2, 2007

  49. [...] details can be found at the WordPress Development Blog which explains the problem and what you could do to help [...]

    Pingback from Footsteps in the Mirror » Attention: Massive WordPress 2.1.1 Exploit. Upgrade To 2.1.2 on March 2, 2007

  50. [...] Para una explicación mas detallada date una vuelta por el post oficial. [...]

    Pingback from GDR Network » Advertencia: WordPress 2.1.1 es Peligroso on March 2, 2007

  51. 升級 WordPress 2.1

    今天終於把部落格升級了,順便也把一干軟體統統升級個夠…

    mysql 4.1.21 升級 5.0.27
    php 4.4.4 升級 5.2.0
    apache 2.0.59 升級 2.2.4
    activeperl 5.8.7 升級 5.8.8 (這不是WordPress必要的)

    WordPress 由 1.5.2 升級…

    Trackback from 精神奕奕 on March 2, 2007

  52. WordPress 2.1.1 gecrackt!

    Wie die WordPress-User ihrem Tellerrand entnehmen können, wird die kürzlich zum Download freigegebenen Update-Version 2.1.1 als gefährlich eingestuft! Ein Cracker hat sich wohl auf dem WordPress-Server zu schaffen gemacht und die Downloa…

    Trackback from BassFireBlog on March 2, 2007

  53. [...] WordPress.org experienced a security-related problem in the last few days. If you’ve downloaded WordPress 2.1.1, you better upgrade to WordPress 2.1.2 now. For more information, read this blog post. [...]

    Pingback from Cyprus Blog Network / Upgrade your WordPress to 2.1.2 now! on March 2, 2007

  54. [...] 2.1.1 then you should immediately upgrade to 2.1.2. A dangerious warning has been issued by WordPress in regards to [...]

    Pingback from BlueFur.com » Update WordPress 2.1.1 Immediately on March 2, 2007

  55. [...] Read more here. [...]

    Pingback from Peter Upfold » Blog Archive » All WordPress 2.1.1 users upgrade now - serious security issue on March 2, 2007

  56. [...] WordPress 2.1.1 Update hat ein böser Cracker bösen Code eingebaut, also fluxifluxi mal schnell auf 2.1.2 updaten und auf guten Code [...]

    Pingback from daniel.hirngespinst.net » Blog Archiv » WordPress 2.1.2 on March 2, 2007

  57. [...] [Fonte WordPress.org] [...]

    Pingback from Aggiornamento critico per WordPress » StormedBrains on March 2, 2007

  58. [...] appena stato reso noto che i file della versione 2.1.1 di WordPress sono stati manomessi qualche giorno fa da un cracker. [...]

    Pingback from Attacco cracker: upgradate a WordPress 2.1.2! at Boliboop on March 2, 2007

  59. [...] I got a scary message when I logged in to the dashboard of one of my blogs tonight to say that the upgrade to WordPress [...]

    Pingback from Urgent WordPress Upgrade - 2.1.2 » Vexentricity on March 3, 2007

  60. [...] you have a WordPress blog, and you upgraded it to 2.1.1 within the last few days, you need to run over and update it 2.1.2 asap. Seems there was a dangerous exploit in 2.1.1 that would blow up the [...]

    Pingback from kirktastic » Blog Archive » Public Service Announcement on March 3, 2007

  61. [...] WordPress.com’s Blog is reporting that WordPress 2.1.1 installations from the past few days are not secure. Apparently their server was hacked and the WordPress master files were changed to open up a [...]

    Pingback from arghyle » Blog Archive » Dangerous! WordPress 2.1.1 on March 3, 2007

  62. [...] Update Note: If you’re a WordPress user and are using version 2.1.1 it is crucial that you upgrade to the latest version (2.1.2) – particularly if you upgraded in the last 3-4 days. The reason is that there has been a hacker compromise that version and add/change code. See details here. [...]

    Pingback from WordPress 2.1.2 now available for download : Meandering Passage on March 3, 2007

  63. [...] was a new release put out by WordPress.org today due to a potential security exploit for anyone that downloaded [...]

    Pingback from WordPress 2.1.1 Dangerous » My New Choice on March 3, 2007

  64. [...] 網路服務 網際網路 資訊科技 請快升級至 WordPress 2.1.2 March 3rd, 2007 這是由 WordPress 官方發出來的消息,簡單地說就是 3 至 4 天前,WordPress 供人下載的 WordPress 2.1.1 裡面有檔案被 [...]

    Pingback from ericsk’s blog » 請快升級至 WordPress 2.1.2 on March 3, 2007

  65. [...] is a post about this on WordPress.org’s Development Blog: This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from   Important: Upgrade to WordPress 2.1.2 by Blogging Pro on March 3, 2007

  66. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Il blog di Gas ® » Hanno fregato WordPress » Blog Archive on March 3, 2007

  67. [...] Read this notice on Wp [...]

    Pingback from WordPress 2.1.1 upgrade it asap! » gh3log on March 3, 2007

  68. WordPress Hacked, Upgrade NOW

    If you were an early adopter and upgraded your WordPress installation to version 2.1.1 you might be running with a severe vulnerability. A cracker got access to the file and edited the code to allow for exploits. Matt has the rest. You can get the down…

    Trackback from PaulStamatiou.com on March 3, 2007

  69. [...] completa en wordpress.org, descargar 2.1.2, [...]

    Pingback from WordPress 2.1.1 Crackeado « Liamngls on March 3, 2007

  70. [...] So kepada sesaper yang baru upgrade ke version 2.1.1 dalam 3-4 hari lepas, sila upgrade ke 2.1.2 secepat mungkin atau kemungkinan website anda akan menghadapi [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 : Eizil.com | Where Information So Valuable on March 3, 2007

  71. [...] If you’re using WordPress 2.1.1, upgrade to 2.1.2 IMMEDIATELY! Share and Enjoy: These icons link to social bookmarking sites where readers can share and [...]

    Pingback from The Marmot’s Hole » Upgrade to WP 2.1.2 NOW!!!! on March 3, 2007

  72. [...] Matt acaba de anunciar hace dos hora el lanzamiento de la nueva versión de WordPress 2.1.2 que, según dice, permanecer en la versión 2.1.1 es muy peligroso debido a un problema grave de seguridad. [...]

    Pingback from WordPress 2.1.2 (actualizar urgente) | PuntoGeek on March 3, 2007

  73. [...] Die Jungs und Mädels haben schnell reagiert und kurzerhand eine bereinigte Version raus gebracht. Mehr Infos dazu gibt es auch bei denen selbst. [...]

    Pingback from Web Zeiger on March 3, 2007

  74. [...] Read full story [...]

    Pingback from WordPress 2.1.1 - Dangerous Download » JaypeeOnline on March 3, 2007

  75. [...] 2.1.2 has officially been released and contains a few security fixes. If you are using WordPress 2.1.1, it is extremely important you update immediately. Download the [...]

    Pingback from SDAC Inc: WordPress Update: 2.1.2 on March 3, 2007

  76. Upgrade immediately to WordPress 2.1.2

    If you haven’t heard already, WordPress’s production server got hacked a couple days ago, and they discovered it today. The cracker put a backdoor into some of the administrative files.
    Anyway, it’s been fixed in the newest release, s…

    Trackback from The Flow of Consciousness on March 3, 2007

  77. [...] all open-source community troubles with hackers happened on a regular basis, but this time, such software as a WordPress was affected, which has [...]

    Pingback from WordPress and open-source community problems on March 3, 2007

  78. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from WordPress 2.1.2 リリース at orioa on March 3, 2007

  79. [...] 3, 2007 at 12:24 am · Filed under Uncategorized WordPress 2.1.1 Security Hole Leaves Blogs Wide Open A hacker managed to sneak into the WordPress server and modify the code in the 2.1.1 release, [...]

    Pingback from WordPress 2.1.1 Security Hole Leaves Blogs Wide Open « Tons of Fresh News on March 3, 2007

  80. [...] It was quite a surprise to see that the WordPress development blog were declaring that their latest release was dangerous. Turns out someone was messing with the original code of our beloved blogging software. Thank goodness for the swift work and dedication of the WordPress team in providing a newer version. If you installed version 2.1.1 (unlike me, I’m just too lazy) then download 2.1.2 now! [...]

    Pingback from Friday’s News: Gack Ink Round 2 And WordPress Troubles :: Unintentionally Blank on March 3, 2007

  81. [...] http://wordpress.org/development/2007/03/upgrade-212/ Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 » Ask Shane.org on March 3, 2007

  82. [...] blocked “theme.php” and “feed.php”, and any query string with “ix=” or “iz=” in it.read more | digg [...]

    Pingback from Living in the Whine Country » Archive » ALERT: WordPress 2.1.1 Security Hole on March 3, 2007

  83. [...] Anda harus upgrade kesemua fail-fail anda ke 2.1.2 secepat mungkin, desak Matt melalui WordPress Dev blog. Hanya efek kepada mereka yang memuat-turun fail WordPress melalui halaman WordPress Download (dalam lingkungan 2-3 hari yang lalu) dan tidak melalui SVN. [...]

    Pingback from WordPress 2.1.1 Merbahaya on March 3, 2007

  84. [...] Breaking news. If you use WordPress 2.1.1 (like we did until very recently) you’ll want to read this. [...]

    Pingback from Ambersail Infosec Roundup » Blog Archive » WordPress 2.1.1 Is Dangerous. Upgrade Now. on March 3, 2007

  85. [...] They’ve done it again. I really like WP but this is getting out of hand. Two hours ago they released a public statement warning users that version 2.1.1 has a dangerous security hole and an immediate upgrade is [...]

    Pingback from Delirium Propaganda » Blog Archive » WordPress upgrade, yet again!!! on March 3, 2007

  86. [...] Wer WordPress in den letzten Tagen gedownloadet hat ist möglicherweise betroffen. Das Update wird dringend empfohlen [...]

    Pingback from Toms Area-X Blog » Blog Archiv » Cracker manipuliert WordPress-Code on March 3, 2007

  87. [...] | WordPress Enlace | [...]

    Pingback from Ya disponible WordPress 2.1.2 - Actualización de Urgencia on March 3, 2007

  88. [...] warning on your dashboard, but in case you haven’t the news is that the latest version has been compromised by a dirty [...]

    Pingback from Science Fiction Robots » Archive » WordPress Hacked, Danger Will Robinson! on March 3, 2007

  89. [...] 2 часа е излезнала новината за нова версия на WordPress. Този път по [...]

    Pingback from И бира » Blog Archive » Upgrade to 2.1.2 on March 3, 2007

  90. [...] 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. Longer explanation: This morning we received a note to our [...]

    Pingback from urks.de // reloaded » wordpress v2.1.1 warnung - exploit gefahr on March 3, 2007

  91. WordPress 2.1.1 dangerous…

    Not only is WordPress 2.1.1 dangerous, it is set to explode.  After releasing WP 2.1.1, someone hacked the WP.org servers, adding a security hole to the release.  The folks at WP immediately responded by removing the malicious code and releasing WP 2…

    Trackback from A Soldier's Mind on March 3, 2007

  92. [...] Cracker inserts security exploit code into WordPress 2.1.1, people advised to upgrade immediately to WordPress 2.1.2. [...]

    Pingback from Bunch of Notes « Silverie on March 3, 2007

  93. [...] If you’re using 2.1.1, read this now. [...]

    Pingback from kev » wordpress 2.1.1 bad. upgrade now. on March 3, 2007

  94. [...] ideale, vi allieto riportandovi il fatto che il blog dei Molesti è stato aggiornato alla versione 2.1.2 di [...]

    Pingback from NerdMolesto in action » molesti.com :: Founded AD MCMXCIX on March 3, 2007

  95. [...] WordPress.org: March 2, 2007 WordPress 2.1.1 dangerous, Upgrade to 2.1.2 By Matt. Filed under [...]

    Pingback from I See Invisible People » WordPress Alert on March 3, 2007

  96. [...] Read more at the WordPress site. If you’re running anything older than v2 you might want to consider upgrading too. [...]

    Pingback from Paul, Kerri and The Boys » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  97. [...] THIS IS A VERY IMPORTANT ANNOUNCEMENT! (Not Joomla Related!) [...]

    Pingback from » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 » Joomla Components Extensions Blog on March 3, 2007

  98. [...] had to update my blog because some idiot decided to screw with the latest release. I hate stuff like this. I bet that guy is feelings pretty good right [...]

    Pingback from Nothing Concept :: Blog :: Scurry, scurry on March 3, 2007

  99. [...] WordPress 2.1.1 Dangerous, Upgrade [...]

    Pingback from Macitreal - WordPress hacked on March 3, 2007

  100. [...] probably affects a *very* small part of our audience, but it’s worth passing along: WordPress 2.1.1 dangerous, Upgrade to 2.1.2. Apparently, a cracker got access to a server and “tweaked” a couple of files. Full [...]

    Pingback from Innovation in College Media » Blog Archive » PSA: WP 2.1.1 upgrade hacked; 2.1.2 available on March 3, 2007

  101. [...] just in from wordpress: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from WordPress 2.1.1 could be hacked : BlissLogs on March 3, 2007

  102. [...] Zitat wordpress.org: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from iKA’s Blog » Wichtiges Update auf WordPress 2.1.2 on March 3, 2007

  103. [...] clipped from wordpress.org [...]

    Pingback from Scott-O-Rama » WordPress 2.1.1 Dangerous, Upgrade Immediately on March 3, 2007

  104. [...] just got THIS popup in my RSS reader, Google Reader Long story short: If you downloaded WordPress 2.1.1 within [...]

    Pingback from WordPress.org hacked/cracked at B L O G . M A C C A R O C K S . C O M on March 3, 2007

  105. [...] 詳情請見官網消息:WORDPRESS 2.1.1 DANGEROUS, UPGRADE [...]

    Pingback from Morton’s Weblog » Blog Archive » WordPress 2.1.1 遭駭客置入 exploitable code on March 3, 2007

  106. [...] you downloaded and installed the recent 2.1.1 version of WP, it is critical that you upgrade to 2.1.2 immediate. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Urgent note for others running WordPress » Home of the Soul Cookie on March 3, 2007

  107. [...] 有更新到 WP 2.1.1 的人請趕快升到 2.1.2 請見官方公告 [...]

    Pingback from 太空猴子::SpaceMonkey » 危險危險 WP 2.1.1 on March 3, 2007

  108. [...] 2.1.1 was hacked, anyone who’s downloaded it in the last 3-4 days should download version 2.1.2 immediately. [...]

    Pingback from Circle Six Blog » Blog Archive » Worpress 2.1.1 Hacked on March 3, 2007

  109. [...] If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. |Read more| [...]

    Pingback from The Voyager - » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  110. [...] parecen nuevos, al personal de WordPress.org les han inflitrado codigo a su ultimo release (WordPress 2.1.1), ahora todos… a actualizar de [...]

    Pingback from 512 Megas » Novatada a WordPress.org on March 3, 2007

  111. [...] From WordPress.org: [...]

    Pingback from Mario’s multimedia… » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  112. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Peter’s Blog » Blog Archive » WordPress 2.1.1 Dangerous on March 3, 2007

  113. [...] WordPress 2.1.1 is Dangerous, Critical Flaw Found [...]

    Pingback from cdharrison.com » Critical WordPress Update on March 3, 2007

  114. [...] [...]

    Pingback from WordPress Francophone » Sortie de WordPress 2.1.2 : Mise à jour de sécurité majeure on March 3, 2007

  115. [...] from WordPress.org: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Eli Burford » Blog Archive » WordPress 2.1.2 - They just keep on coming. on March 3, 2007

  116. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from blog.emerick.org » upgrade to 2.1.2 on March 3, 2007

  117. [...] this week I upgrade the backend to the latest version of WordPress 2.1.1. Today WordPress announced that a hacker had inserted a remote PHP exploit into the code and recommended everyone to upgrade [...]

    Pingback from DanLin.net » WordPress 2.1.1 security flaw found and patched on March 3, 2007

  118. [...] el blog de desarrolo de WordPress nos informan de que si has descargado WordPress 2.1.1 durante los 4-5 días pasados, es muy [...]

    Pingback from WeblogToolsCollection Español » Blog Archive » Atención: actualiza a WordPress 2.2 YA on March 3, 2007

  119. [...] leitura do artigo sobre o assunto é altamente [...]

    Pingback from WordPress 2.1.2 :: bernabauer.com - Noticias de Tecnologia todos os dias. on March 3, 2007

  120. [...] WordPress has deemed the entire release as dangerous. You can download the patched version here. http://wordpress.org/download and you can get the full stoty here. http://wordpress.org/development/2007/03 [...]

    Pingback from The Truth About Internet Marketing » WordPress 2.1.1 Security Flaw on March 3, 2007

  121. [...] saw an announcement on the dashboard that the latest version of WordPress (version 2.1.1) had been classified as Dangerous and the download and the server it was stored on had been taken down and everyone who recently [...]

    Pingback from Just Thinkin’ » Blog Archive » Everything Went Down–What a Day! on March 3, 2007

  122. [...] Obširnejši opis varnostne luknje. [...]

    Pingback from Mario’s thing… » WordPress 2.1.2 - nujna nadgradnja! on March 3, 2007

  123. [...] 剛剛發佈緊急公告,指出由於其中一台提供下載的 server 被駭客入侵,在先前發佈的 2.1.1 [...]

    Pingback from stOOrz » WordPress 2.1.2 released on March 3, 2007

  124. [...] those running WordPress 2.1.1, this is an urgent upgrade available due to a critical security flaw. Overwrite your old WP files as soon as [...]

    Pingback from Hari’s Corner » Urgent message to WordPress users on March 3, 2007

  125. [...] is the first time I did upgrade so fast. The event is here. I checked the files are on 2/26, so my blog should be safe. But I don’t want to take the [...]

    Pingback from Living Better BLOG » Emergency Upgrading to WordPress 2.1.2 on March 3, 2007

  126. [...] of the week:) (fake smily) You might wan to upgrade to 2.1.2 if you’re using the 2.1.1.  And here is the link to the news on what happened that causes this security [...]

    Pingback from Searchtified.com » Blog Archive » *phew…Just updated to WP 2.1.2 on March 3, 2007

  127. [...] doubt this news will be all over before the day is out, but it is worth spreading this announcement all the same. [...]

    Pingback from A Mind @ Play » WordPress 2.1.1 vulnerability on March 3, 2007

  128. [...] Source: WordPress blog [...]

    Pingback from //beconfused » Blog Archive » Upgrade to WordPress 2.1.2 on March 3, 2007

  129. [...] upgrade files for 2.1.2 Because of the highly unusual nature of the security breach at wordpress.org that resulted in the zip and tar.gz for WordPress 2.1.1 having malicious code [...]

    Pingback from No upgrade files for 2.1.2 « Mark on WordPress on March 3, 2007

  130. [...] Read more about WordPress Upgrade [...]

    Pingback from WordPress 2.1.2 update is released at Petes Blog on March 3, 2007

  131. [...] as soon as I move up to 2.1.1 of course they discover an exploit. Here is more on the story from WordPress. Luckily though for once I actually read the Dashboard when I started up the Admin screen and saw [...]

    Pingback from Life Is Risky » Blog Archive » Alert! WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  132. [...] enero se liberaba WP 2.1; hace apenas 10 días aparecía la versión 2.1.1… y ya tenemos la versión 2.1.2. Está claro que WordStress no está hecho para espíritus sensibles al sobresalto. Por un lado, [...]

    Pingback from Mangas Verdes » Sorpresa, sorpresa… ya esta aquí WordPress 2.1.2 on March 3, 2007

  133. [...] WordPress 2.1.1 dangerous, upgrade [...]

    Pingback from Webmaster Libre | WordPress 2.1.2 ¿pero qué está pasando? on March 3, 2007

  134. [...] being a fan and user of WordPress here is some pretty big news from the Official WordPress blog, WordPress 2.1.1 Dangerous, Upgrade: This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from Everybody Knows » Blog Archive » Urgent Upgrade Notice - WordPress 2.1.1 on March 3, 2007

  135. [...] like a hacker managed to sneak an exploit into the WordPress 2.1.1 blogging software. If you downloaded it within the past few days your files may include a security [...]

    Pingback from stefpause.com » Blog Archive » Security exploit in WordPress 2.1.1 on March 3, 2007

  136. [...] Their story is: WORDPRESS 2.1.1 DANGEROUS, UPGRADE [...]

    Pingback from Untwisted Vortex - Living in a Different Land » Upgrade to WordPress Version 2.1.2 Right Now! on March 3, 2007

  137. [...] read this announcement immediately if you’ve updated to 2.1.1 within the last few days. It’s quite likely you [...]

    Pingback from Digital Ramble » Blog Archive » attention all WordPress 2.1.1 upgraders… on March 3, 2007

  138. [...] very important security issue with WordPress 2.1.1 was just announced a few hours [...]

    Pingback from britton blog - an american student in galway, ireland » Important: WordPress 2.1.1 is a Security Threat on March 3, 2007

  139. [...] they are saying WordPress 2.1.1 is dangerous: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from import this. » Blog Archive » WP 2.1.1 security issue on March 3, 2007

  140. [...] 今天早上看到官方的消息,在之前服务器被黑客登录并修改了WP2.1.1中的两个文件,以方便黑客获取服务器管理权限。官方的人认为整个2.1.1都是不安全的,需要立即更新到2.1.2,并且将新文件全部覆盖那些旧的。 [...]

    Pingback from 凡人弄 : Blog Archive : WP2.1.1遭遇CRACK,紧急更新 on March 3, 2007

  141. [...] WordPress— [...]

    Pingback from OpinionBug.com » WordPress 2.1.1 Compromised By Cracker on March 3, 2007

  142. [...] you have already upgraded to WordPress 2.1.1, your site might include code for letting someone else control your blog, that was added in a break in. There is a new release available that removes the malicious code. [...]

    Pingback from Red Alert: Upgrade WordPress To 2.1.2 on iface thoughts on March 3, 2007

  143. [...] If you’ve downloaded the release version of 2.1.1 (e.g. the .zip or .tar.gz version of the fil…upgrade to the new release pronto. [...]

    Pingback from ShadowLife » Blog Archive » WordPress 2.1 release source compromised on March 3, 2007

  144. [...] y como indican en la web de WordPress, parece ser que algun cracker graciosillo les ha entrado en el servidor y les ha modificado los [...]

    Pingback from Actualización urgente de WordPress 2.1.1 a 2.1.2 at luigix.com on March 3, 2007

  145. 赶紧更新WP 2.1.1

    如果你前几天刚更新WP到2.1.1,那么请赶紧升级吧.
    WP服务器被黑,里面被黑客加入了可以远程执行的代码.

    Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security expl…

    Trackback from 赵明亮.你太有才了! on March 3, 2007

  146. [...] Related Links: – WordPress 2.1.1 dangerous, Upgrade [...]

    Pingback from Rxbbx Blog WordPress 2.1.2 on March 3, 2007

  147. [...] og der er tale om en ikke-planlagt opdatering. Helt uhørt har en hacker været så uvenlig at lave noget kode om i version 2.1.1 på WordPress.org inden for de sidste dage. Den danske version skulle dog ikke være blevet [...]

    Pingback from WordPress 2.1.2 er udgivet at WordPress DK on March 3, 2007

  148. [...] 雖然說升級是上禮拜的事情,收到消息說 WordPress 2.1.1 下載檔案被 cracker 放東西進去,可能有安全性疑慮,請大家升級到 2.1.2。官方的網誌也說明他們的作法:WordPress 2.1.1 Dangerous, Upgrade。 [...]

    Pingback from WordPress 2.1.2 緊急發佈 « Kirin Lin on March 3, 2007

  149. [...] WordPress 2.1.2 has been released and I have updated this site to WordPress 2.1.2. [...]

    Pingback from GaMerZ.WordPress » Blog Archive » WordPress 2.1.2 on March 3, 2007

  150. [...] the story of what this was all [...]

    Pingback from Unplanned downtime on March 3, 2007

  151. [...] pointed out on the WordPress development blog, a cracker gained access to the wordpress.org servers and replaced the 2.1.1 download with a [...]

    Pingback from wordpress.org Cracked, Exploit in 2.1.1 Release | no wow on March 3, 2007

  152. [...] said This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from BuzzDroid.com » WordPress 2.1.1 Unsafe - Upgrade Now Or Your Blog May Die! on March 3, 2007

  153. [...] 2.1.2 にアップグレードしたほうが良いです。というのも、WordPress 公式サイトによると If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a [...]

    Pingback from 43hr.org » Blog Archive » さくらインターネットで EasyWPUpdate を使う on March 3, 2007

  154. [...] ha anunciado Matt desde el propio blog oficial del proyecto, la versión 2.1.1 que se liberó hace unos días, y de la que como siempre os informé en este [...]

    Pingback from Urgente actualización a WordPress 2.1.2 » ChochitoPelao on March 3, 2007

  155. [...] I finally get around to upgrading to the latest and greatest version of WordPress, and it was compromiesd! I’m now up to [...]

    Pingback from jefflundberg.com/blog » Blog Archive » WordPress 2.1.2 on March 3, 2007

  156. [...] aproximadamente 3 horas fue anunciado que la versión 2.1.1 de WordPress contiene múltiples vulnerabilidades, por este motivo se recomienda la actualización a la versión [...]

    Pingback from Cortex’s Secret Blog on March 3, 2007

  157. [...] It was determined that a cracker had gained user-level access to one of the servers that powers wordpress.org, and had used that access to modify the download file. We have locked down that server for further forensics, but at this time it appears that the 2.1.1 download was the only thing touched by the attack. They modified two files in WP to include code that would allow for remote PHP execution. – Full Story [...]

    Pingback from Upgrade your WordPress 2.1.1 into 2.1.2 ASAP by Reaper-X .:[ ID ]:. on March 3, 2007

  158. [...] was a serious breach of blog software WordPress’s security the other day. Today it was discovered, and the WordPress.org support forums were down while they [...]

    Pingback from Abandoned Stuff by Saskboy » Blog Archive » WordPress server cracked on March 3, 2007

  159. [...] Para mais informações veja o anúncio oficial. [...]

    Pingback from WordPress 2.1.1 perigoso, atualize para 2.1.2 - Nerd Games on March 3, 2007

  160. [...] WordPress 官方的的消息,Wordpress 2.1.1 [...]

    Pingback from CODE|源码 » WordPress2.1.1 dangerours,upgrade on March 3, 2007

  161. [...] could undermine your blog system and you are advised by the WordPress developers to immediately upgrade to WordPress 2.1.2. According to the WordPress official blog: If you downloaded WordPress 2.1.1 within the past 3-4 [...]

    Pingback from Dangerous exploit in WordPress 2.1.1 at Emporium Blog on March 3, 2007

  162. [...] March 2, 2007 at 10:41 pm · Filed under Blogathon 2007 Taken from the Official WordPress Blog [...]

    Pingback from Angel Lights » WordPress 2.1.2 on March 3, 2007

  163. [...] announced tonight that an unknown hacker inserted a security exploit into 2.1.1. The attack occurred over the past couple of days, but to ensure absolute security the WordPress [...]

    Pingback from Huge WordPress 2.1.1 Security Hole Found · cavemonkey50.com on March 3, 2007

  164. [...] to the WP dudes for the security warning. 2.1.2 successfully [...]

    Pingback from dangerouslyawesome » 2.1.2 upgrade on March 3, 2007

  165. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from McGrew Security on March 3, 2007

  166. [...] เมื่อเจอข่าวนี้ครับ WordPress 2.1.1 dangerous, Upgrade to 2.1.2 ที่ประกาศจากทีมผู้พัฒนาโดยตรง [...]

    Pingback from ใครใช้ WordPress 2.1.1อัพเกรดด่วน - iDayBlog on March 3, 2007

  167. [...] 原因詳見:官網的安全性通知 [...]

    Pingback from 【WP】wordpress 2.1.1的安全性問題 | Robbin.cc on March 3, 2007

  168. [...] keep on top of things here at weknowhtml. thanks to the warning, we’ve upgraded this (and our client blogs) to [...]

    Pingback from the blog: tagging isnt just for hoodlums anymore » and another upgrade on March 3, 2007

  169. [...] joden!!! apenas hace 10 días atrás que WordPress 2.1.1 fue liberado y para colmo de males, ya hay nueva version de WordPress, la 2.1.2. Resulta que un cracker obtuvo acceso a uno de los servidores de wordpress.org y logro modificar el [...]

    Pingback from Increible: WordPress 2.1.1 Crackeado! y WordPress 2.1.2 Liberado « Javier Aroche on March 3, 2007

  170. [...] 2.1.1 has been tampered by some cracker and contains exploitable code. Everyone on that bandwagon should move to 2.1.2 ASAP [...]

    Pingback from hackd » Blog Archive » happens to everyone on March 3, 2007

  171. [...] WordPress Upgrade Released WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2: This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from jimmitchell.org » Archive » Critical WordPress Upgrade Released on March 3, 2007

  172. [...] guys at WordPress have issued an alert to all users who downloaded WordPress 2.1.1 in the past 3-4 days to upgrade [...]

    Pingback from TechnoBeta Blog » Upgrade to WordPress 2.1.2 Immediately! on March 3, 2007

  173. WordPress 2.1.1 berbahaya

    Kaget saya melihat judul dari entri di WordPress development blog: WordPress 2.1.1 dangerous, Upgrade to 2.1.2. Karena menurut Matt, file download-an wordpress 2.1.1 telah diubah oleh cracker sehingga file tersebut memiliki security exploit. Masih menu…

    Trackback from rendra.net. on March 3, 2007

  174. [...] 危险的wordpress2.1.1,赶紧升级! 今天登录后台,看到了一条吓人一跳的消息,wordpress2.2.1版竟然因为服务器被人入侵,给人改了文件,里面放了恶意代码,官方呼吁大家赶紧升级至2.1.2版本 [...]

    Pingback from 波乐阁 | 危险的wordpress2.1.1,赶紧升级! on March 3, 2007

  175. [...] More information: WordPress 2.1.1 dangerous, Upgrade to 2.1.2. [...]

    Pingback from Hariadi.NET » WordPress 2.1.1 Dangerous on March 3, 2007

  176. [...] can view the whole article on wordpress’s website « New Strain of Virus a Threat to Businesses [...]

    Pingback from » Bloggers, Update your WordPress Immediately on March 3, 2007

  177. [...] कर रहे हैं। वर्डप्रेस के द्वारा जारी नई खबर के अनुसार वर्डप्रेस का अब तक का [...]

    Pingback from वर्डप्रेस 2.1.1 “खतरनाक” है at इधर उधर की on March 3, 2007

  178. [...] For more info, visit the official WordPress Development Blog. [...]

    Pingback from WordPress 2.1.1 is dangerous - esn studio on March 3, 2007

  179. [...] 2.1.1, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [hat tip: Evan] [...]

    Pingback from WordPress 2.1.1 and 2.0.9 Bugfix on March 3, 2007

  180. [...] This is the kind of thing you pray never happens, but it did and now we’re dealing with it as best we can. Although not all downloads of 2.1.1 were affected, we’re declaring the entire version dangerous and have released a new version 2.1.2 that includes minor updates and entirely verified files. We are also taking lots of measures to ensure something like this can’t happen again, not the least of which is minutely external verification of the download package so we’ll know immediately if something goes wrong for any reason. Source: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from WordPress Pwned Tips Dr.com on March 3, 2007

  181. [...] peeps have at WordPress announced a very critical update WordPress 2.1.1 users. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from WordPress 2.1.2 Critical Update! on March 3, 2007

  182. [...] poor WordPress developers are having continuing problems with the 2.0 release. A security alert was issued on the WordPress Development Blog on March 2, 02007 for anyone who’s downloaded [...]

    Pingback from The Ten Thousand Year Blog » Security alert: update your WordPress 2.1.1 installation on March 3, 2007

  183. [...] the WordPress Multiple Script Injection Vulnerabilities in yesterday’s Quick Link, and today WordPress is reporting that a cracker gained user-level access to one of the servers and modified the 2.1.1 download file. [...]

    Pingback from Security Tools News & Tips » Blog Archive » WordPress 2.1.1 Dangerous, Upgrade on March 3, 2007

  184. [...] the WordPress Multiple Script Injection Vulnerabilities in yesterday’s Quick Link, and today WordPress is reporting that a cracker gained user-level access to one of the servers and modified the 2.1.1 download file. [...]

    Pingback from Security Tools News & Tips » Blog Archive » WordPress 2.1.1 Dangerous, Upgrade on March 3, 2007

  185. [...] a few days after version 2.1.1, WordPress released version 2.1.2 because the previous version may include a security exploit that was added by a [...]

    Pingback from Important! Upgrade your WordPress to 2.1.2! on March 3, 2007

  186. [...] out the door for a business fishing trip (more in the next post) but just wanted to let all you WordPress users know that you need to upgrade to 2.1.2 now! Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from O’Flaherty - » Major security issue with WordPress 2.1.1 - Upgrade to 2.1.2 now! on March 3, 2007

  187. [...] WordPress is reporting that a cracker gained user-level access to one of the servers and modified the 2.1.1 download file. The hacker managed to modify two files in WP 2.1.1 to include code that would allow for remote PHP execution. The 2.1.1 package does not seem to have been compromised when it was initially released, WordPress encourages all users to upgrade to 2.1.2 to patch the security hole. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from WordPress 2.1.1 Dangerous, Upgrade - Nirlog.com - Technology, Life and other stuff that come along… on March 3, 2007

  188. [...] Source: WordPress [...]

    Pingback from FahadBlog » Blog Archive » WordPress securety hole on March 3, 2007

  189. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [Wordpress.org] [...]

    Pingback from KhimHoe.Net » Blog Archive » [!]Wordpress 2.1.2! Security Exploit in 2.1.1! on March 3, 2007

  190. [...] I suppose I’m glad I didn’t even have a chance to start. Today, just about everyone with WordPress 2.1.1 was scrambling to upgrade it after it was revealed that intentionally malicious code had been placed in it. I’d encourage people to read the original announcement. [...]

    Pingback from Original Cin » Blog Archive » WordPress 2.1.2, BBpress, and Why FanCruft is Still Hand-Rolled For the Foreseeable Future on March 3, 2007

  191. [...] it was initially released, WP encourages all users to upgrade to 2.1.2 to patch the security hole.read more | digg [...]

    Pingback from 煎蛋 » WordPress 2.1.1 Security Hole Leaves Blogs Wide Open on March 3, 2007

  192. [...] a 2.1.1, cambiate de inmediato a 2.1.2 para tu seguridad y la de tu blog. Más información en: WordPress.org Filed under Noticias, WordPress having Leave a [...]

    Pingback from Weas Frikis » Blog Archive » Actualización Crítica usuarios de WordPress 2.1.1 on March 3, 2007

  193. [...] include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 [...]

    Pingback from WordPress Exploit at Rule Of One on March 3, 2007

  194. [...] 本家WordPress 2.1.1のファイルがクラックされていたとのことで、 緊急アップデートがアナウンスされております。 http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from くろいおとなどっとこむブログ » WordPress 2.1.2へアップデートを!(警告) on March 3, 2007

  195. [...] 「WordPress」官方於幾小時前緊急釋出了 WP 升級版本「2.1.2」, 主因是「2.1.1」的下載主程式被 Crack, 某些檔案被加入了用來遠程運行 PHP 的程式。(詳情) [...]

    Pingback from Goston’s Blog » [BLOG] 升級成 WordPress 2.1.2 on March 3, 2007

  196. [...] sitting there in the News and Announcements block of the admin page was an emergency notice. Some *@#!*%# mashuga cracked root on WordPress.org’s servers and slipped some malware code [...]

    Pingback from New Harper’s Mews » Blog Archive » WordPress Servers Cracked; Version 2.1.1 Compromised on March 3, 2007

  197. [...] altered, so users of WordPress 2.0.9 should be safe. More information on this issue can be found here. Read the Favored Freeware entry for WordPress [...]

    Pingback from MacManX.com | Urgent WordPress Security Update v2.1.2 on March 3, 2007

  198. [...] I upgrade WordPress 2.1.1 to 2.1.1 [...]

    Pingback from OK1JKT - Web pages » Blog Archive » Security upgrade WP 2.1.1 to 2.1.2 on March 3, 2007

  199. [...] download the new version, put the files back in place, then watch as my life slowly fades away. Read the full article here Make sure you upgrade your WordPress installation.  Why?  Because you touch yourself at night. [...]

    Pingback from .::v-nessa.net::. » WordPress 2.1.1 is Dirty on March 3, 2007

  200. [...] Dies betrifft nur die englische Version von WordPress, die DE-Edition 2.1.1 ist davon nicht betroffen. Mehr Informationen unter WordPress 2.1.1 und der “worst case” und WordPress 2.1.1 dangerous, Upgrade to 2.1.2. [...]

    Pingback from Tigions Blog » Blog Archive » ! WordPress 2.1.1 security exploit on March 3, 2007

  201. [...] sivustoa pyörittävän WordPressin versio 2.1.1 julistettiin vaaralliseksi hakkerin onnistuttua muuttamaan sen koodia yhdellä wordpress.org:n servereistä. [...]

    Pingback from Spacealien.fi » Blog Archive » Pikapäivitys WordPressiin on March 3, 2007

  202. [...] Matt has posted a long explanation for this: If your blog is running 2.1.1, please upgrade immediately and do a full overwrite of your old files, especially those in wp-includes. Check out your friends blogs and if any of them are running 2.1.1 drop them a note and, if you can, pitch in and help them with the upgrade. [...]

    Pingback from OpenAppDotOrg: Open Source Blogging Applications on March 3, 2007

  203. [...] 请尽快更新到2.1.2 据官方blog通知 wordpress的下载服务器被入侵 修改了wp内几个文件 [...]

    Pingback from 探花 @ Tinn Walk » 请立即更新wordpress2.1.2 on March 3, 2007

  204. [...] If you upgraded to version 2.1.1 within the last three or four days (as I spent a few hours doing on Thursday), you need to upgrade again to 2.1.2. There’s a major security problem with the earlier version. See here. [...]

    Pingback from SeoulLife.net » WordPress alert on March 3, 2007

  205. [...] have updated their version to 2.1.2 to address a security breach with the 2.1.1 version of the WordPress Installer Download [...]

    Pingback from o! Just Me » WordPress 2.1.1 has security holes, upgrade on March 3, 2007

  206. [...] scivolata per il team di WordPress.org: nell’annuncio per la versione 2.1.2 leggiamo che “se avete scaricato la versione 2.1.1 negli ultimi 3-4 giorni, i tuoi file potrebbero [...]

    Pingback from WordPress 2.1.1 "crackato", passare subito a 2.1.2 on March 3, 2007

  207. [...] the WordPress.org download site and included some ways to exploit your site. Read about it on the WordPres Dev blog, but first start downloading [...]

    Pingback from WordPress Hacked! » mattwiebe.com on March 3, 2007

  208. [...] For more info, head over to WordPress.Org [...]

    Pingback from Meshio.Com- Managing Your Personal Finance the Malaysian Way! » Blog Archive » WordPress 2.1.1 Upgrade Dangerous on March 3, 2007

  209. [...] WordPress announced that the WordPress v2.1.1 is corrupted and those who upgraded their sites to that version should upgrade the system to the v2.1.2 immediately. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from WordPress v2.1.1 Cracked, Upgrade To v2.1.2 Immediately » SELaplana on March 3, 2007

  210. [...] WORDPRESS 2.1.1 DANGEROUS, UPGRADE 혹, 2.1.1을 사용하시는 분이 있다면 빨리 업그레이드 하세요. [...]

    Pingback from AINUERON.SHOUTORANGE » Blog Archive » [긴급]워드프레스 2.1.1 는 2.1.2로 업그레이드 하세요. on March 3, 2007

  211. [...] the official WordPress blog for [...]

    Pingback from Viper007Bond.com » Blog Archive » ATTENTION WORDPRESS 2.1.1 USERS! on March 3, 2007

  212. [...] Update ASAP, WP Download page. [...]

    Pingback from TechZOnline.net » Critical Update on WordPress, 2.1.2 on March 3, 2007

  213. [...] party to include code, which allows the execution of arbitrary PHP code on the remote blog hosting. Here’s the news. I created this post with the only aim to spread the word, so that everybody involved may upgrade [...]

    Pingback from WordPress 2.1.1 download was modified by hacker(s): upgrade to 2.1.2 » Autarchy of the Private Cave on March 3, 2007

  214. [...] per risolvere il problema e per rilasciare una nuova versione. Leggo inoltre dal messaggio sul blog degli sviluppatori che d’ora in poi sarà aggiunto un sistema di verifica esterna al download di tutti i file [...]

    Pingback from Attenzione! Aggiornate il vostro WordPress, un cracker aveva modificato i file della versione 2.1.1 | MondoBlog on March 3, 2007

  215. [...] you are running WordPress 2.1.1, then there is some bad news. According to annoucement on WordPress blog, a cracker managed to add some security expoit files in archive of wordpress [...]

    Pingback from Upgrade to WordPress 2.1.2 NOW on March 3, 2007

  216. [...] Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code [Quelle….weiterlesen] [...]

    Pingback from      m68n,wengophone and fun » wordpress 2.1.1 dangerous, upgrade to 2.1.2 on March 3, 2007

  217. [...] [via WordPress Blog] [...]

    Pingback from WordPress 2.1.2 Released, Critical update » Freakitude on March 3, 2007

  218. [...] Les mer om saken på WordPress.org WordPress 2.1.1 Dangerous, upgrade [...]

    Pingback from WordPress 2.1.2 - Viktig sikkerhetsoppgradering | Norsk WP on March 3, 2007

  219. [...] can see the official announcement here. blog, [...]

    Pingback from Why you should upgrade to WordPress 2.1.2 :: Cucirca.com on March 3, 2007

  220. [...] there has been a whoopsie with some of their download-servers, so you might want to make shure, you’re upgrading to the newest version (2.1.2, as we speak). as always, it’s trouble-free. just upload everything to your server and visit yourserver/wp-admin/upgrade.php. [...]

    Pingback from habi.gna.ch » update your wordpresses! on March 3, 2007

  221. [...] Fuck. This. Shit. [...]

    Pingback from Sho Fukamachi Online » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  222. [...] 3.3.: Ja, da bin ich ja mal froh, daß ich auf eine Version mit Backdoor upgedated hatte. Danke an Jörn für den Hinweis. Wenn das mal nicht zum Kotzen ist, was ist es [...]

    Pingback from #!/bin/blog :: tar, rm, cp on March 3, 2007

  223. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Ellen Burgess » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  224. [...] For anyone running a recently upgraded Blog with WP 2.1.1, please upgrade to 2.1.2. [...]

    Pingback from Running WP 2.1.1? Upgrade immeditely! at BlogThe.Net on March 3, 2007

  225. [...] niet goed is gevalideerd en problemen kan veroorzaken. Helaas blijft het hier niet meer bij, want gisteren werd duidelijk dat de website van WordPress aangepast was waarbij versie 2.1.1 was voorzien van modificaties die [...]

    Pingback from Dailystuff » Hoe veilig is WordPress on March 3, 2007

  226. [...] that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. Bron __________________ . . . [...]

    Pingback from Worpress Exploit - webhostingtalk.nl on March 3, 2007

  227. [...] 10:08, Posted in Pelit ja vehkeet, Aamu sitten alkoi mukavasti tällaisella varoituksella. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Yksi näkökulma » WordPress 2.1.2 on March 3, 2007

  228. [...] la última semana que sepas que tienes un pequeño problema que resolver. Algo así es lo que dicen en su blog oficial. Por lo visto un cracker ha tenido acceso al código de esta versión durante los últimos días y [...]

    Pingback from Un lugar en el mundo… » Blog Archive » Actualización de seguridad para WordPress 2.1.1 on March 3, 2007

  229. [...] had released their WordPress 2.1.2today, but sadly it’s is not a feature upgrade, instead it’s an emergency security upgrade due to [...]

    Pingback from WordPress 2.1.2: Emergency Security Upgrade at hwa2u.com on March 3, 2007

  230. [...] Plus d’infos : http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Le blog de Xavier … » Blog Archive » WordPress : mise à jour importante (2.1.2) on March 3, 2007

  231. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from my weblog » Blog Archive » WordPress 2.1.1 released on March 3, 2007

  232. [...] WordPress 2.1.1 Dangerous. Upgrrrrrrrrrade! Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from boogher.com - » Spread the word! on March 3, 2007

  233. [...] je kort geleden WordPress hebben geupdate naar 2.1.1 moet je vooral dit even lezen: It was determined that a cracker had gained user-level access to one of the servers [...]

    Pingback from WordPress 2.1.1 is onveilig at TibsBits on March 3, 2007

  234. [...] Muutettu versio sallii PHP-koodin suorittamisen palvelimella verkon yli. Tarkempi kuvaus tapahtumista ja ongelmasta on WordPressin Developer Blogissa. [...]

    Pingback from WordPress 2.1.1 on vaarallinen - Kimmo Suominen on March 3, 2007

  235. [...] are the WordPress developers so sporadic in releasing WP? Well, To see the full answer, visit the WordPress Development Blog for the full [...]

    Pingback from WordPress 2.1.2 Released at forgedeuphoria.com on March 3, 2007

  236. [...] For further details check out the WordPress blog. [...]

    Pingback from PureBlogging.com » WordPress 2.1.1 is Dangerous, Upgrade Now! on March 3, 2007

  237. [...] leerse el comunicado desde el sitio de WordPress. Realmente, es sorprendente que esto haya ocurrido. En lo personal, aún no logro comprender cómo [...]

    Pingback from Crackean la descarga oficial de WordPress » Redes de Blogs on March 3, 2007

  238. [...] gaat snel, vandaag is er alweer een nieuwe versie van WordPress uitgekomen, versie 2.1.2. Iemand heeft toegang gehad tot de server van WordPress en daar een versie neergezet [...]

    Pingback from Zomaar… » Blog Archive » Alweer nieuwe versie on March 3, 2007

  239. [...] 2.1.1 is potentially dangerous because some cracker got his paws on it. Doggone cracker! So upgrade to 2.1.2. Got it? Although, you’ll notice I’m still [...]

    Pingback from Weblog Sin Pies » wordpress users: be warned! on March 3, 2007

  240. Strano l’aggiornamento a WordPress 2.1.2…

    Oggi apro come solito il pannello di amministrazione del mio Blog, che si vasa su WordPress. E noto, nella parte dedicata agli avvisi degli sviluppatori, un avviso che mi fa rizzare le orecchie.
    L’avviso è quello che trovate a questo link: http:…

    Trackback from Il Blog di Orebla on March 3, 2007

  241. [...] doesn’t matter if you installed 2.1.1 on the first day it came out, well before the cracker modified the file on wordpress.org. WordPress 2.1.2 has a security fix that 2.1.1 doesn’t have. And it has several fixes that [...]

    Pingback from WordPress 2.1.2 is a mandatory upgrade « Mark on WordPress on March 3, 2007

  242. [...] Hier geht’s zur Downloadseite für WordPress 2.1.2 – und hier zur entsprechenden WordPress-Meldung. [...]

    Pingback from Steini’s Garden » Blog Archive » WordPress - gefährliches Sicherheitsloch! on March 3, 2007

  243. [...] scivolata per il team di WordPress.org: nell’annuncio per la versione 2.1.2 leggiamo che “se avete scaricato la versione 2.1.1 negli ultimi 3-4 giorni, i tuoi file [...]

    Pingback from WordPress 2.1.1 “crackato”, passare subito a 2.1.2 « L’urlo del coniglio on March 3, 2007

  244. [...] and inserted exploit code into version 2.1.1 of WordPress. They are therefore recommending that everyone upgrade from version 2.1.1 to version [...]

    Pingback from whatithink on March 3, 2007

  245. [...] escasas horas ha sido publicada una actualización de seguridad letal para todos aquellos que hayan instalado WordPress 2.1.1 en [...]

    Pingback from Los crackers se la cuelan a WordPress.org — Criando Cuervos on March 3, 2007

  246. [...] More on that on the official wordpress blog. [...]

    Pingback from WordPress 2.1.1 was qualified as dangerous! .:. eDragonu - the choice of a personal path on March 3, 2007

  247. [...] acaba de publicar la versión 2.1.2, tan sólo unos días después de la 2.1.1. ¿El motivo? Un cracker se ha colado en el servidor del [...]

    Pingback from Actualiza inmediatamente a WordPress 2.1.2 » La brujula verde on March 3, 2007

  248. Angriff auf WordPress-Installationspaket

    Wer in den letzten Tagen die WordPress-Version 2.1.1 von wordpress.org heruntergeladen hat, tut gut daran raschmöglichst auf die neue Version 2.1.2 upzudaten:
    Es wurde festgestellt, das sich ein Cracker Zugriff auf einen der “wordpress.org&#822…

    Trackback from BloggingTom on March 3, 2007

  249. [...] cuentan en la web de desarrollo de wordpress. algún cracker se coló en sus servidores y modificó el código de la versión 2.1.1. incluyendo [...]

    Pingback from Dondado » Peligros en la versión 2.1.1 de WordPress on March 3, 2007

  250. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Dando la chapa » Crackeada descarga oficial de WordPress 2.1.1 on March 3, 2007

  251. [...] More details here. [...]

    Pingback from Liberty Alone » Blog Archive » WordPress security vulnerability on March 3, 2007

  252. [...] hacker was able to add a vulnerability to the version of 2.1.1 that was pushed out about a week or so ago. Essentially, it was a back door [...]

    Pingback from john bollwitt blog » WordPress 2.1.1 bad, WordPress 2.1.2 good on March 3, 2007

  253. [...] Download-Dateien für WordPress 2.1.1 verändert. Also hat das WordPress-Team mal schnell noch ein Update 2.1.2 rausgehauen, das man auf jeden Fall installieren [...]

    Pingback from Soundmonster’s Blog » Blog Archiv » …und noch ein WordPress-Update :-) on March 3, 2007

  254. [...] WordPress 2.1.1 Dangerous, upgrade to 2.1.2 [...]

    Pingback from flipthedolphin · Danger with WordPress 2.1.1 - Imperative Upgrade to 2.1.2 on March 3, 2007

  255. [...] ທີ່ມາ – WordPress.org [...]

    Pingback from WordPress v2.1.2 - An Emergency Update | au8ust’s tech channel on March 3, 2007

  256. [...] recent 2.1.1 release of the popular blog software WordPress was compromised by a cracker who made it easier for to execute code remotely. This is interesting because the official release was quietly and subtly compromised, and has been [...]

    Pingback from Voice of Valehru » Important WordPress Anouncement. on March 3, 2007

  257. [...] WordPress heeft bezoek gehad van een ongenode gast die toegang heeft verworven tot de servers en ver…. Hierdoor is er nu een nieuwe versie beschikbaar (2.1.2) die alle problemen moet oplossen. [...]

    Pingback from WordPress 2.1.1 gevaarlijk · Bakkel dot com on March 3, 2007

  258. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from WordPress 2.1.2 at ogeeBloggin’ on March 3, 2007

  259. [...] in den vergangenen Tagen Zugriff auf die Dateien verschafft und sie für seine Zwecke verändert (offizielle Stellungnahme hier). Zwar betrifft dies offenbar nicht die eingedeutsche Fassung (”DE-Edition”), ein [...]

    Pingback from UPLOAD » Schwere Sicherheitslücke in WordPress 2.1.1 on March 3, 2007

  260. [...] Sorry. Alle bitte WordPress updaten. [...]

    Pingback from Code Candies » Blog Archive » WordPress updaten on March 3, 2007

  261. [...] dei server di WordPress è risultato compromesso (fonte): un cracker ha avuto accesso alla macchina e modificato i file del pacchetto WordPress 2.1.1 [...]

    Pingback from pseudotecnico:blog » Blog Archive » URGENTE: aggiornate a WordPress 2.1.2!! on March 3, 2007

  262. [...] ein echter Alptraum für die betroffenen User und erst recht für das WordPress-Team. Das ist kein Joke, siehe auch [...]

    Pingback from Basic Thinking Blog » der GAU - infizierte Originaldateien: DRINGEND WordPress 2.1.1 UPDATEN!!!! on March 3, 2007

  263. [...] auf die zweifelhafte (aber nicht manipulierte) DE-Version 2.1.1 die aktuelle Version 2.1.2 von offizieller Seite nachgeschoben. Diese Version soll die erheblichen Sicherheitsmängel beheben. WordPress 2.1.2 ist [...]

    Pingback from blog.babytux.de » WordPress 2.1.2 on March 3, 2007

  264. WordPress 2.1.2 mise à jour recommandée

    J’ai tout d’abord pensé à un poisson d’avril. Mais c’est encore un peu tôt.

    Pour les utilisateurs de WordPress, il est vivement recommandé de faire la mise à jour de WordPress 2.1.1 à la version 2.1.2.

    Apparemment, une personne malveill…

    Trackback from Gatellier.be on March 3, 2007

  265. [...] Dev blog announcement. Essentially, someone got into the WordPress install hosted on the servers and made some modifications to a couple of files. Malicious changes at that. The information in the blog post seems to indicate that feed.php and theme.php (both in wp-includes) were modified. Perhaps other files were as well. [...]

    Pingback from The Lair / wordpress 2.1.1 exploitable in the worst way on March 3, 2007

  266. [...] N’attendez pas et allez voir le site web WordPress. [...]

    Pingback from » WordPress 2.1.1 - Information de sécurité on March 3, 2007

  267. [...] read more | digg story [...]

    Pingback from WordPress 2.1.1 Security Hole Leaves Blogs Wide Open « Know things on March 3, 2007

  268. [...] tespit edildi. Bu durum üzerine WordPress.org gerekli düzenlemeleri yapıp 2.1.2 sürümünü yayınladı. Eğer son 3-4 gün içinde WordPress.org’dan İngilizce son sürümü indirip kurduysanız [...]

    Pingback from WordPress Türkiye » Blog Archive » WordPress 2.1.2 on March 3, 2007

  269. [...] here, you may want to subscribe to my RSS feed. Thanks for visiting!If your blog uses WordPress, this advisory should be read and acted [...]

    Pingback from The Social Programmer - Craig Murphy: author, blogger, community evangelist, developer, speaker » WordPress 2.1.2 - immediate upgrade advisory on March 3, 2007

  270. [...] issue on v2.1.1 as per WordPress.org (just read their short story and anyone who use WordPress will rush to upgrade!). So I quickly stop [...]

    Pingback from Dozleng.com Internet Security & Others on March 3, 2007

  271. [...] you use WordPress version 2.1.1, a dangerous security breach in that version has been [...]

    Pingback from WordPress 2.1.2 - Essential upgrade at NevilleHobson.com on March 3, 2007

  272. WordPress 2.1.1 infiziert – deutsche Version nicht betroffen

    Im Developers Blog von WordPress.org kann man es nachlesen:
    Vor kurzem konnte ein Hacker Zugriff auf den offiziellen WordPress-Server nehmen und die dort gelagerte Version 2.1.1 von WordPress infizieren.
    Wer also in den letzten Tagen WordPress 2.1.1 di…

    Trackback from Pottblog on March 3, 2007

  273. [...] sehr beunruhigende Nachricht habe ich gerade im Blog des WordPress-Entwicklerteams gelesen: Offenbar wurde einige Files des [...]

    Pingback from mikrosklave.net » Blog Archive » Gecracktes WordPress-Update on March 3, 2007

  274. [...] 2.1.2 has been compromised. If you installed it recently you should immediately upgrade. This is from the official WordPress [...]

    Pingback from Copacetic » Blog Archive » WordPress 2.1.2 Compromised on March 3, 2007

  275. WordPress 2.1.1 pericoloso, aggiornate alla 2.1.2!

    Per coloro che hanno scaricato – negli ultimi 3-4 giorni – ed installato la versione 2.1.1 di WordPress è vivamente consigliato di aggiornare tutti i file con la nuova versione 2.1.2 immediatamente.

    Il motivo di questa urgenza? Un cracker si è intro…

    Trackback from lucatogni.ch on March 3, 2007

  276. [...] פרטים יש פה.  « לכתוב ליד [...]

    Pingback from מסעותיו של מרק בשבילי החיים » ארכיון » בעית אבטחה אפשרית בוורדפרס 2.1.1 on March 3, 2007

  277. [...] Read here the whole story [...]

    Pingback from PCNews.TV » Blog Archive » WordPress 2.1.1 IS dangerous, Upgrade to 2.1.2 on March 3, 2007

  278. [...] motivo di questa urgenza? Un cracker si è intromesso nei server di WordPress.org ed ha caricato una [...]

    Pingback from Massimo D’Onofrio » WordPress 2.1.1 pericoloso, aggiornate alla 2.1.2! on March 3, 2007

  279. [...] sull’accaduto qui e download sul sito [...]

    Pingback from :: Michelangeblog :: WordPress 2.1.1 compromesso, AGGIORNATE! on March 3, 2007

  280. [...] Mar, 2007  General If’ you’re running WP 2.1.1 you need to update your files urgently.  There may be a serious security hole in some downloads of [...]

    Pingback from A critical WordPress patch « Tom’s View of the World on March 3, 2007

  281. [...] wordpress.org spiegano che un cracker è riuscito ad entrare su uno dei server di wp.org e ha modificato alcuni [...]

    Pingback from Wolly Weblog » WP 2.1.2 nuovo aggiornamento OBBLIGATORIO dato che la 2.1.1 è stata dichiarata pericolosa on March 3, 2007

  282. [...] The distribution for WordPress 2.1.1 was hacked to include an exploit which would allow remote users to take run malicious code on a webserver. This has been fixed, and an updated issued, for more details, see this post. [...]

    Pingback from Murky.org » WordPress 2.1.1. should be updated immediately on March 3, 2007

  283. [...] sich in den letzten Tagen WordPress 2.1.1 heruntergeladen und installiert hat sollte auch dringend updaten, denn ein gewiefter Cracker hat sich vor kurzem an den Dateien von Verison 2.1.1 vergangen und ein [...]

    Pingback from Peter Kröner - Webdesign, HTML, CSS, PHP » Archiv » Neue Versionen von Exaile und WordPress. on March 3, 2007

  284. [...] Üble Geschichte bei WordPress: Ein Bösewicht hatte die Download-Datei des bis gestern aktuellen WordPress 2.1.1 manipuliert und eine Lücke eingeschleust. Auch wenn man wohl nicht betroffen war, wenn man 2.1.1 kurz nach dem Release heruntergeladen hatte, wurde 2.1.1 generell für gefährlich erklärt und Version 2.1.2 freigegeben. Mehr dazu. [...]

    Pingback from Das BlogBlog · WordPress 2.1.2 on March 3, 2007

  285. [...] quick note to point out that TD Word Count is compatible with v2.12 of WordPress announced and released yesterday. This is an important security update for WordPress 2.1.1 users, so I would [...]

    Pingback from WordPress 2.12 compatibility at TD Scripts WordPress mods on March 3, 2007

  286. [...] 3rd, 2007 @ 12:25 by Mike A notice on the WordPress development blog says that the WordPress 2.1.1 download package was corrupted by [...]

    Pingback from devBlog » WordPress 2.1.1 download corrupted! on March 3, 2007

  287. Peligro! WordPress 2.1.1 fue Hackeado.

    Al parecer WordPress 2.11 fue hackeado desde hace unos 3 o 4 días por un Hacker quien agrego un Exploit dentro de los archivos… Es Inminente y necesaria la Actualizacion a WP 2.1.2.

    Trackback from www.elrincondejesus.com on March 3, 2007

  288. [...] Read more about the unfortunate event at WordPress.org. [...]

    Pingback from Soulreaper.net - The blog of certain uncertainties » Blog Archive » WordPress.org hacked - update your blogs! on March 3, 2007

  289. [...] selanjutnya di :  http://wordpress.org/development/2007/03/upgrade-212/ Social Bookmark- SelectBlinkList del.icio.us Digg it Furl ma.gnolia Netvouz RawSugar Shadows [...]

    Pingback from WordPress Malaysia » Blog Archive » Bahaya! Naiktaraf segera ke WP 2.1.2! on March 3, 2007

  290. [...] a heads up to anyone else who runs WordPress, there’s a new release 2.1.2 available. Some versions of 2.1.1 may have been exploited by a cracker to allow remote execution of code. [...]

    Pingback from WordPress Upgrade at SDJL.co.uk on March 3, 2007

  291. [...] copy that has been tampered with to create security holes. According to the announcement on WordPress Blog, a cracker managed to get user-level privileges on the WordPress.org server and changed some of the [...]

    Pingback from Inspirated » Serious security concerns for WordPress 2.1.1 users on March 3, 2007

  292. [...] version 2.1.1 (like me) you need to upgrade immediately to 2.1.2. Read the WordPress announcement here (or check your dashboard). Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 [...]

    Pingback from Upgrade WordPress-- Place of Stuff on March 3, 2007

  293. [...] the off chance that you haven’t heard the news yet. You should upgrade your WordPress install straight away. Don’t hesitate, do it now. [...]

    Pingback from You didn’t hear? Upgrade now! at Holy Shmoly! on March 3, 2007

  294. [...] diesem Artikel ist die Version 2.1.1, ein Bugfix-Release für 2.1, vor einigen Tagen kompromittiert [...]

    Pingback from Das Schandblatt » Blog Archive » WordPress 2.1.1 gefährlich on March 3, 2007

  295. [...] Si parla di un cracker che si è introdotto nei server di wp ed ha modificato la versione 2.1.1 inserendo degli exploit. Quindi, l’aggiornamento deve essere fatto il prima possibile. [...]

    Pingback from WordPress 2.1.1 bacato! Aggiornarlo subito con la 2.1.2 at Daniele Salamina on March 3, 2007

  296. [...] (2.1.1) is not safe for use and widely opened to malicious attack. Here’s the excerpt from WordPress’ blog. This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from Eches Blog » Important: Upgrade to WordPress 2.1.2 on March 3, 2007

  297. [...] Mullenweg has pubished an important post to the WordPress Blog.  The recent WordPress 2.1.1 update was comprised by a cracker and code was [...]

    Pingback from WordPress 2.1.1 is “dangerous” - Upgrade to 2.1.2 now! at Wired Gecko on March 3, 2007

  298. [...] WordPress 2.11 is dangerous, upgrade to 2.12 now [...]

    Pingback from Vanilla Days : Old rundown bridge on March 3, 2007

  299. [...] WordPress compromised. [...]

    Pingback from Black Company Studios » Blog Archive » Not good. Then good. on March 3, 2007

  300. [...] üzerine WordPress.org gerekli düzenlemeleri yapıp 2.1.2 sürümünü yayınladı. Eğer son 3-4 gün içinde WordPress.org’dan İngilizce son sürümü [...]

    Pingback from gKAANs.oRg | WP 2.1.2 Çıktı [ ÖNEMLİ OKUYUNUZ ] | on March 3, 2007

  301. [...] Que tenía bicho dentro. [...]

    Pingback from Desesperación on March 3, 2007

  302. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Weblog von Jakob Albrecht » Blog Archiv » Shit happens… on March 3, 2007

  303. [...] die Übersetzung des offiziellen Statements aus dem Entwickler-Blog: Die ganze Geschichte in Kurzfassung: Wenn ihr WordPress 2.1.1 in den letzten 3 bis 4 Tagen [...]

    Pingback from macosbrain » Blog Archive » WordPress 2.1.1 und der “worst case” on March 3, 2007

  304. [...] Full explanation. I’ve done the upgrade even though my installation was older. You never know. [...]

    Pingback from Embarassing: WordPress hacked at teezeh dot de on March 3, 2007

  305. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from Stefan Beyer » WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  306. [...] WordPress I ragazzi di Wp hanno avuto un problema di sicurezza, chi ha installato la versione 2.1.1 farebbe meglio a passare subito alla 2.1.2. Tag:cms cracker [...]

    Pingback from Livingston, il blog di Marco Mazzei / Aggiornare WordPress on March 3, 2007

  307. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from WordPress2.1.1に重大なセキュリティーホール « yanalog.net on March 3, 2007

  308. [...] hacked: where do we go from here? By Tim WordPress founder Matt Mullenweg reports the bad news: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Tim Anderson’s ITWriting - Tech writing blog » WordPress hacked: where do we go from here? on March 3, 2007

  309. [...] In urma cu aproximativ 14 ore WordPress.org au dat un anunt prin care avertizeaza ca versiunea wordpress 2.1.1 disponibila la download pe serverul lor in ultimile 3-4 zile are fisiere ce contin un exploit. Din cate spun ei cracker-ul ar fi fost o persoana cu access la serverul wordpress.org , acest lucru permitandu`i sa modifice doua fisiere. Irelevant acum cine a fost crackerul. Important este ca toti care au descarcat si instalat wp. 2.1.1 in ultimile zile sa-si faca upgrade urgent. [...]

    Pingback from Stealth Settings » WordPress 2.1.1 / C(rack)orrupted release files on March 3, 2007

  310. [...] scritto anche nella dashboard di wordpress, però per i più distratti segnalo questa notizia . In pratica qualche cracker burlone ha sfruttato una vulnerabilità del loro webserver per [...]

    Pingback from HARDBOILED.IT » Blog Archive » Aggiornate WordPress! on March 3, 2007

  311. [...] WordPress admitted that some nefarious individual broke into the download site for WordPress and changed some includes [...]

    Pingback from WordPress reminder that software confidence not limited to Second Life » VTOR - Virtual TO Reality on March 3, 2007

  312. [...] Scherz, ein Blick in den WordPress-Blog zeigt’s: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a [...]

    Pingback from The Tryary WS » WordPress 2.1.1: Infizierte Originaldateien on March 3, 2007

  313. [...] Schlechte Nachrichten: Wer WordPress “während der letzten 3-4 Tage” auf Version 2.1.1 upgedatet hat, darf sich die Mühe nochmal machen – und sollte dringend ein Auge auf seine Datenbank werfen: Offenbar hatte ein Cracker Schreibzugang zur 2.1.1 Release-Version und konnte eine kompromittierte Version in Umlauf bringen, welche das das Einschleusen von PHP-Code ermöglicht. [...]

    Pingback from AX-11 » WordPress 2.1.1 - Update war kompromittiert on March 3, 2007

  314. [...] Read the full story at the WordPress blog. [...]

    Pingback from Toxic Web Blog - Ramblings of a Toxic mind... Dangerous upgrade… on March 3, 2007

  315. [...] wordpress.org Popularity: [...]

    Pingback from WordPress 2.1.2 erschienen » Sebbis Blog on March 3, 2007

  316. [...] WordPress 2.1.1 dangerous, upgrade [...]

    Pingback from Smemoratezze dal sottosuolo » Blog Archive » E questo succede a casa WordPress on March 3, 2007

  317. [...] podnie¶æ WP do 2.1.1 a tu okazuje siê, ¿e konieczne jest przej¶cie o wersjê wy¿ej, poniewa¿, jak pisz± w og³oszeniu, nawali³o bezpieczeñstwo i jaki¶ cracker podmieni³ pliki na zawieraj±ce exploita. nie dotyczy to [...]

    Pingback from vermin.eu.org » Konieczny security upgrade WP do 2.1.2 on March 3, 2007

  318. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Tales from the Longbox » Blog Archive » WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  319. [...] to WP 2.1.1 in the last few days, you’re WP installation could potentially be vulnerable. Matt explains over at the WordPress Blog… Long story short: If you downloaded WordPress 2.1.1 within the [...]

    Pingback from Have WordPress 2.1.1? Panic!! « The Opti Mystic on March 3, 2007

  320. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from iBiOBiZiGOP » Blog Archive » Temporary blog, viruses and WP dangers. on March 3, 2007

  321. [...] lyckats kompromettera den förra versionen av uppgraderingen av WordPress. Så här skriver man på WordPress.org. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Gastronaut » WordPress 2.1.1 komprometterat av hackare on March 3, 2007

  322. WordPress security problem

    Thanks wordpress team for fast advertising.
    I found this message today on my Dashboard of WordPress WordPress 2.1.1 dangerous, Upgrade to 2.1.2
    http://wordpress.org/development/2007/03/upgrade-212/
    I upgraded, and it was straight simple. Since I rely o…

    Trackback from Mohamed Ibrahim on March 3, 2007

  323. [...] Hmz. Goed dat ik het nagelaten heb om 2.1.1 aan mij voorbij te laten gaan. Normaal ben ik er als de kippen bij, maar deze keer had ik het wat laten aanslepen. Geen goesting om weer die ganse dans uit te voeren en zo. [...]

    Pingback from Netsensei » Blog Archive » Gevaarlijk on March 3, 2007

  324. [...] Εγω αναβαθμιστικα παντως. Περισσοτερες πληροφοριες εδω In: διαφορα | Mindblog this | Cull [...]

    Pingback from Paradise Lost » Επειγουσα αναβαθμιση wordpress σε 2.12 on March 3, 2007

  325. [...] ini saya buka wp-admin untuk menulis, hanya perhatian saya terganggu dengan berita berjudul “WordPress 2.1.1 Dangerous, Upgrade to 2.1.2“. Aduh! Ada apa lagi sih ini? Baru beberapa hari yang lalu saya upgrade blog ini dengan [...]

    Pingback from Catatan » WordPress 2.1.1 is Dangerous!! on March 3, 2007

  326. [...] like WordPress 2.1.1 had a security exploit that allowed remote PHP [...]

    Pingback from WordPress 2.1.1 compromised at odrakir.com on March 3, 2007

  327. [...] WordPress Dangerous Upgrade [...]

    Pingback from Lehrerzimmer » Blog Archive on March 3, 2007

  328. [...] WordPress via Shell The word is already out that WordPress 2.1.1 is severely vulnerable and you have to upgrade to WordPress 2.1.2 to keep your blog [...]

    Pingback from Upgrading WordPress via Shell » Techtites on March 3, 2007

  329. [...] (重大そうなんで「WordPress 2.1.1 dangerous, Upgrade to 2.1.2」を日本語訳。この文章での一人称は、私 Dai やこのサイトではなく、Matt や WordPress開発チームのことです。) [...]

    Pingback from DOHC. · WORDPRESS 2.1.1 は危険、2.1.2へ更新を!! on March 3, 2007

  330. [...] And if you haven’t upgraded to 2.1.2 yet, then please do so immediately to ensure that your WordPress 2.1 installation doesn’t get hacked. (No Ratings Yet)  Loading [...]

    Pingback from Weblog Tools Collection » Blog Archive » Upgrade WordPress via Shell on March 3, 2007

  331. [...] It was determined that a cracker had gained user-level access to one of the servers that powers wordpress.org, and had used that access to modify the download file. We have locked down that server for further forensics, but at this time it appears that the 2.1.1 download was the only thing touched by the attack. They modified two files in WP to include code that would allow for remote PHP execution. More on this story from WordPress.org [...]

    Pingback from Blog Flak - Blog Resources » Blog Archive » WordPress 2.1.1 Contains Security Exploit on March 3, 2007

  332. [...] but hadn’t got around to downloading, 2.1.1, and it seems that I was lucky because the WordPress blog has news that their distribution server has been hacked and an exploit was added to the code available [...]

    Pingback from WordPress site hacked… pictures at eleven » the billblog on March 3, 2007

  333. [...] hetki sitten tätäkin sivustoa pyörittäneen WordPressin versionumero 2.1.1 julistettiin vaaralliseksi hakkerin onnistuttua muuttamaan pari päivää sitten kyseisen version [...]

    Pingback from munhiekkis.fi - Mun hiekkis…Mun moottoripyörä ! ! » Tärkeä pikapäivitys WordPressiin on March 3, 2007

  334. [...] 2.1.2 çıktı!! İki günde bir yeni versionu çıkyor. Bu adreste dediğine göre 2.1.1 sürümünde bir problem varmış, hacklenebilirmişiz, mutlaka [...]

    Pingback from WordPress 2.1.2 çıktı!! - Omeragacan.Com - Blog on March 3, 2007

  335. [...] If you use WordPress and your on version 2.11 you MUST upgrade as soon as possible. A hacker managed to insert a security exploit into the 2.11 files. Although this only happened in the last 3-4 days it makes sense to move to 2.12…NOW. The dev blog has all the details. [...]

    Pingback from WordPress…stuff at iand.net on March 3, 2007

  336. [...] Full announcement over at WordPress.org [...]

    Pingback from Potentional flaw in WordPress 2.1.1. | GregRobson.co.uk on March 3, 2007

  337. [...] none of my sites running off of wordpress are on 2.1.1 – but this is bound to cause some problems. Details here. Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Aric Watson » Yikes on March 3, 2007

  338. [...] you are running WordPress v2.1.1 you need to upgrade now! Read their announcement here. This is more serious than your normal round of ’someone found another way to exploit sloppy [...]

    Pingback from LibertyNews.org - Liberty and Freedom for All » Serious WordPress Security Hole in v2.1.1 on March 3, 2007

  339. [...] הדיווח בבלוג הפיתוח של וורדפרס מסתבר כי אתמול בבוקר נתקבלה [...]

    Pingback from אלעד בבלוגלי » ארכיון הבלוג » וורדפרס 2.1.1 מסוכן - תעדכנו מהר on March 3, 2007

  340. [...] the official announcement: It was determined that a cracker had gained user-level access to one of the servers that powers [...]

    Pingback from WordPress 2.1.1 Includes Exploitable Code - Sheeped on March 3, 2007

  341. [...] Источник: WordPress.org [...]

    Pingback from PHP Devils » WordPress 2.1.1 Dangerous, Upgrade Now! on March 3, 2007

  342. [...] Article Link [...]

    Pingback from Liquidmatrix Security Digest on March 3, 2007

  343. [...] According to this security announcement from WordPress, a server hosting WordPress downloads was recently compromised, and a cracker modified the 2.1.1 [...]

    Pingback from PreshBlog - » WordPress 2.1.1 considered dangerous, upgrade now! on March 3, 2007

  344. Damn crackers suck!

    Looks like the WordPress 2.1.1 download was compromised. I’m not sure if the download I had was the compromised version, but it never hurts to be safe, so I upgraded all the blogs I look after to the latest version.

    Obviously the script kiddies…

    Trackback from This Geek on March 3, 2007

  345. [...] was upgraded. WordPress (including this blog) was upgraded – twice in 36 hours. Old junk was deleted. Remember, I am always looking for people to help maintain Xinki so everyone [...]

    Pingback from Gary Kirk » Blog Archive » Upgrades on March 3, 2007

  346. [...] 2.1.1 er tilsyneladende direkte farlig. En opdatering til 2.1.2 anbefales derfor på det kraftigste. [...]

    Pingback from WordPress 2.1.2 — spiri.dk — Blog og personligt site for Søren Hugger Møller on March 3, 2007

  347. [...] to the WordPress security exploit I mentioned earlier, WaggishBLOG was taken offline for just under ten minutes this afternoon as I [...]

    Pingback from Gary Kirk » Blog Archive » WaggishBLOG on March 3, 2007

  348. [...] Alla som uppdaterat ska genast uppdatera igen. Ett säkerhetshål har hittats. Med info: http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from pettzon » Blog Archive » problem med version 1.1 on March 3, 2007

  349. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Biker|Geek » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2!!! on March 3, 2007

  350. [...] Današnji dnevni pogled na news agregator me je dobro trgnuo iz učmalosti. Naime, na jedan od WordPress servera je izvršen napad, koji je za poslediicu imao kompromitovanje arhive sa engineom verzije 2.1.1. Preuzete arhive poseduju sigurnosne propuste, pa je vrlo bitno uraditi upgrade na verziju 2.1.2. Problematični server je van pogona, a više o ovome ovde i ovde. [...]

    Pingback from Escape to freedom » Blog Archive » Upgrade pod hitno! on March 3, 2007

  351. [...] فوق قسمتی از خبری است که در بخش توسعه و انتشار وب سایت رسمی وردپرس اعلام [...]

    Pingback from Alvanweb » به‌ روز رسانی وردپرس on March 3, 2007

  352. [...] WordPress crew were fast to react to the news and have released a statement, which states that they have boycotted the release of WordPress 2.1.1 as they don’t know [...]

    Pingback from WordPress Security Vulnerability « Post Archive « www.lattimore.id.au on March 3, 2007

  353. [...] In the interest of getting the word out as quickly and as widely as possible, a brief word about a new WordPress release: If you recently installed version 2.1.1, you should upgrade to WordPress 2.1.2 immediately. There was a security breach on the server which housed the download archives, and some files in the 2.1.1 download were modified to include a serious security hole. There are more details in the official WordPress Dev Blog announcement. [...]

    Pingback from geek ramblings » Important: Upgrade to WordPress 2.1.2 on March 3, 2007

  354. [...] Sorta lazy, but also sorta cautious. Turns out it’s a good thing I haven’t installed WordPress 2.1.1… if you use WordPress for your blog (and I’m not talking about WordPress.com), [...]

    Pingback from It’s all Good. » 3 Good Dots Saturday… on March 3, 2007

  355. [...] morning I found a security advisory for WordPress 2.1.1, it seems the file was corrupted on the wordpress server. Not taking any risk, considering I found [...]

    Pingback from The Joop Manoeuvre revisited… at Ruben’s blik op Verweg on March 3, 2007

  356. [...] If you have recently updated your blog to wordpress version 2.1.1, please immediately upgrade to 2.1.2 – as per this WORDPRESS EXPLOIT ALERT. [...]

    Pingback from WordPress Version 2.1.1 Hacked - MAJOR VULNERABILITY ALERT - UtheGuru.com on March 3, 2007

  357. ¡Actualicen sus blogs! WordPress 2.1.1 es peli…

    Matt, en la página de WordPress, reporta que si has descargado WordPress 2.1.1 en los últimos 3 o 4 días, los archivos podrían contener una violación de seguridad agregada por un cracker, y por lo tanto debes actualizar todos los archivos a la versió…

    Trackback from Sozter! on March 3, 2007

  358. WordPress 2.1.1 declared “dangerous”…

    Matt over at the WordPress blog writes: “Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediatel…

    Trackback from guillermoesteves.com on March 3, 2007

  359. [...] Fonte: WordPress.org [...]

    Pingback from DropsTech.org » Blog Archive » Falha de Segurança: WordPress 2.1.1, Atualize para o 2.1.2 Imediatamente on March 3, 2007

  360. [...] code in wordpress 2.1.1 Acourding to the wordpress weblog, a hacker managed to switch latest.zip with his version that includes some malicious code of some [...]

    Pingback from Cracker code in wordpress 2.1.1 « Virus In Training on March 3, 2007

  361. [...] Die Version 2.1.1 von WordPress wurde auf Grund eines sehr unschönen Vorfalles als „gefährliches Risiko” eingestuft und somit wird jedem Anwender eine sofortige Aktualisierung auf die Version 2.1.2 empfohlen. Ein offizielles Statement der Entwickler gibt es dort: http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from gefährliches Risiko « Enrico.Kalkbrenner.name/ on March 3, 2007

  362. [...] managed to slip some bad code into the latest download for WordPress which was at version 2.1.1. According to the official WordPress Blog, this may allow a security exploit on your blog if and only if you’re running that version. [...]

    Pingback from WordPress 2.1.1 Is Dangerous at FreshBlogger on March 3, 2007

  363. [...] See the blog post for more information: http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from purposemakers » WordPress download hacked, security exploit added added… on March 3, 2007

  364. [...] denn nur die Version 2.1.1 war anscheinend betroffen. Wer die ganze Story lesen möchte, kann das im WP Blog tun. Ach ja, und natürlich solltet ihr euer WordPress auch [...]

    Pingback from KOPIS.DE » Blog Archive » Sicherheitslücke in WP 2.1 on March 3, 2007

  365. [...] From wordpress.org: [...]

    Pingback from For WordPress 2.1.1 users: download 2.1.2 immediately : SMILING PEANUT web hosting on March 3, 2007

  366. [...] has been a security breach and you need to upgrade again immediately. All of the details are at WordPress.org but here’s a quick snippet: Long story short: If you downloaded WordPress 2.1.1 within the [...]

    Pingback from Just a Small Pair » WordPress Security Breach on March 3, 2007

  367. [...] has been a security breach and you need to upgrade again immediately. All of the details are at WordPress.org but here’s a quick snippet: Long story short: If you downloaded WordPress 2.1.1 within the [...]

    Pingback from WordPress Security Breach at Clueless Wonder on March 3, 2007

  368. [...] you recently upgraded to WordPress 2.1.1, you might have a version of the code with a big security hole. WP recommends upgrading immediately to [...]

    Pingback from Off Topic :: WordPress 2.1.1 security hole on March 3, 2007

  369. [...] WordPress Development Blog: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 ..This is the kind of thing you pray never happens, but it did and now we’re dealing with it as best we can.. [...]

    Pingback from Kishore Balakrishnan’s Blog » Blog Archive » WordPress 2.1.1 is dangerous on March 3, 2007

  370. [...] after reading the security upgrade release (you should upgrade now, especially if you installed 2.1.1 in the past 3-4 days) of [...]

    Pingback from » Upgrade WordPress to 2.1.2 / mattwalters.net on March 3, 2007

  371. [...] more at : http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Nestle Poell's Recipe for a Chocolatey Life » Get rid of WordPress 2.1.1 on March 3, 2007

  372. WordPress 2.1.1 Vulnerable

    Suben al servidor de wordpress version con vulnerabilidad, upgrade urgente.

    Trackback from www.enchilame.com on March 3, 2007

  373. [...] read the story [...]

    Pingback from blogasys » WordPress 2.1.1. Dangerous Upgrade on March 3, 2007

  374. [...] No, not all downloads are affected, but it is better to be safe than sorry. The current latest release, 2.1.2, addresses this vulnerability.  For more information, see this post. [...]

    Pingback from habibbijan.com » Using WordPress 2.1.1? Please upgrade on March 3, 2007

  375. [...] downloadable from WordPress.org to upload and install on a web server, NOT wordpress.com), please visit this page about upgrading your [...]

    Pingback from Totem To Temple » Attention Christian Bloggers Running WordPress on March 3, 2007

  376. [...] use, or you could find your website replaced with p0rn or casino ads. (WordPress 2.11 users — leave now and read this. [...]

    Pingback from Keep your website secure without breaking a sweat at mblair's Website Optimization Cafe on March 3, 2007

  377. [...] Sideblog If you recently upgraded or installed WordPress 2.1.1 please read this security upgrade notice and upgrade to 2.1.2 immediately. I love so many things about this Montessori style nursery [...]

    Pingback from Kerflop » WordPress Security Upgrade Notice on March 3, 2007

  378. [...] offline for a few hours earlier today due to a security exploit in WordPress. WordPress’ official blog issued a warning about a compromised version that had been available from the WordPress [...]

    Pingback from WordPress Website compromised - Lead to down time at Open Source Notebook on March 3, 2007

  379. [...] another WordPress security problem, and this one’s a doozy.  I’m happy that they’re keeping people informed, but dang, this software takes waaaay [...]

    Pingback from Jim Carson » Blog Archive » WordPress 2.1.2 update on March 3, 2007

  380. [...] never a good thing when you find out your blog software’s been hacked — even worse when your first notice of the fact is from slashdot! But I don’t feel too [...]

    Pingback from AllensOnThe.Net » Security Notifications on March 3, 2007

  381. [...] If you’re new here, you may want to subscribe to my RSS feed. Thanks for visiting!If you are using WordPress 2.1 it is vital that you download the latest upgrade, especially if you downloaded your copy of WP2.1 within the last few days. A major security exploit has been discovered which leaves your blog open to attack, to read more and grab the upgrade, go here. [...]

    Pingback from kate blogs about writing & web design » Blog Archive » WordPress Users: Very Important, Please Read on March 3, 2007

  382. [...] If you’re new here, you may want to subscribe to my RSS feed. Thanks for visiting!If you are using WordPress 2.1 it is vital that you download the latest upgrade, especially if you downloaded your copy of WP2.1 within the last few days. A major security exploit has been discovered which leaves your blog open to attack, to read more and grab the upgrade, go here. [...]

    Pingback from kate blogs about writing & web design » Blog Archive » WordPress Users: Very Important, Please Read on March 3, 2007

  383. [...] 2.1.1 version of WordPress (and if you aren’t, why not?). Then you need to read and act upon this advisory immediately. Hat tip to Craig for pointing it out to [...]

    Pingback from garyshort.org - » Urgent WordPress Advisory on March 3, 2007

  384. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from ICeman » Estamos hasta las manos on March 3, 2007

  385. [...] 2.1.2 Update – Security Update • Posted: Mar 03, 07 From the WordPress.org Blog: “Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files [...]

    Pingback from WordPress 2.1.2 Update - Security Update | TheDocBlog Webmaster Resource : WordPress 2.1.2 Update - Security Update on March 3, 2007

  386. [...] NOW before your blog is [...]

    Pingback from Tetromino weblog » Blog Archive » If you are running WordPress 2.1.1 on March 3, 2007

  387. Leichtsinnige WordPress-Admins

    Argl. gerade über einen peinlichen Hack bei wordpress.org gelesen.
    Wieso können die nicht ihre Pakete signieren? Dann wäre es aufgefallen, ich bin sicher. Und wieso können die keine Patches anbieten, die man ganz einfach mit patch (1) einspielen ka…

    Trackback from Rainers Blog on March 3, 2007

  388. [...] 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.” message and a stack of RSS coverage of an exploit of the version of WP [...]

    Pingback from Steven Milne » Blog Archive » WordPress close call on March 3, 2007

  389. [...] 2.1.1: Bad News Seems a cracker has tainted the source for WP 2.1.1.  Good thing I hadn’t yet upgraded.  Anyone who did should go get 2.1.2 immediately. Tagged [...]

    Pingback from WordPress 2.1.1: Bad News » Another Blogger on March 3, 2007

  390. [...] atualização: a notícia completa pode ser lida em “WordPress 2.1.1 Dangerous, Upgrade“ [...]

    Pingback from URGENTE: WordPress 2.1.2 | Escrita Torta em Linha Reta on March 3, 2007

  391. [...] newbies y demás que se les ocurra intentar explotar la vulnerabilidad surgida recientemente en WP 1.1. Así que ya os lo aviso para que no perdáis el tiempo, que dicen que es oro Tags: blog, wordpress, [...]

    Pingback from GHalician’s Space » Este blog NO es vulnerable on March 3, 2007

  392. [...] It appears that WordPress 2.1.1 has been backdoored in such a way that anyone using it (downloaded it in the past 2-3 days) can be easily compromised via explicitly made vulnerable feedback.php and theme.php files. More on it here. [...]

    Pingback from SecuriTeam Blogs » WordPress 2.1.1 backdoored on March 3, 2007

  393. [...] Good lord, this is a nightmare scenario. If you run a website powered by WordPress, be sure to read this announcement: [...]

    Pingback from WordPress users, take notice | Ed Bott’s Windows Expertise | on March 3, 2007

  394. [...] 1 Meldung auf WordPress.org [...]

    Pingback from daheads blog² » Blog Archive » Wichtiges Sicherheitsupdate für WordPress 2.1 on March 3, 2007

  395. [...] WordPress.org got hacked, and the unwanted guests changed the 2.1.1 release files around, adding a severe security hole. I find it interesting that they use the word “cracker” [...]

    Pingback from WordPress.org Got Hacked // shorty114.net on March 3, 2007

  396. [...] Technorati | EMail This Post • Print This Post Bloggers using WordPress 2.1.1 are urged to upgrade to version 2.1.2 immediately, Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Journal of Intercultural Learning » Blog Archive » Upgrade! WordPress 2.1.1 compromised by a cracker. on March 3, 2007

  397. [...] For those of you running WordPress and haven’t heard already, upgrade to 2.1.2!! Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. – WordPress.org [...]

    Pingback from Darth Cena v.13 Where the Streets Have No Name on March 3, 2007

  398. [...] Full story here Share and Enjoy:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]

    Pingback from Yet Another WordPress Security Hole on March 3, 2007

  399. [...] about WordPress is how responsive the community is. To that end if your running WordPress 2.1.1 HEED this ANNOUNCEMENT from the WordPress Development Blog: If you downloaded WordPress 2.1.1 within the past 3-4 days, [...]

    Pingback from Urgent! If you have WordPress 2.1.1 upgrade to 2.1.2 - Beck’s Cafe - Pull up a chair for coffee & chit chat on life, gender, technology & our world on March 3, 2007

  400. [...] about WordPress is how responsive the community is. To that end if your running WordPress 2.1.1 HEED this ANNOUNCEMENT from the WordPress Development Blog: If you downloaded WordPress 2.1.1 within the past 3-4 days, [...]

    Pingback from Urgent! If you have WordPress 2.1.1 upgrade to 2.1.2 - Beck’s Cafe - Pull up a chair for coffee & chit chat on life, gender, technology & our world on March 3, 2007

  401. [...] êáêÜ ðáéäéÜ Ýêáíáí ðÜëé æçìéÜ ìå èýìá áõôÞ ôçí öïñÜ ôï WordPress. ÊÜðïéïò êáôÜöåñå íá áðïêôÞóåé ðñüóâáóç êáé íá áëëÜîåé áñ÷åßá óå [...]

    Pingback from Wordrpess 2.1.2 áìÝóùò!!! - pestaola.gr on March 3, 2007

  402. [...] auch auf wordpress.org zu lesen ist wird ein Update auf Version 2.1.2 dringend angeraten: Long story short: If you [...]

    Pingback from mein Notizblog » WordPress: Upgrade auf Version 2.1.2 dringend angeraten on March 3, 2007

  403. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Figuaccia di WordPress… Aggiornate gente, aggiornate (tags: wordpress blogging) [...]

    Pingback from links for 2007-03-03 « Il blog di lucacicca on March 3, 2007

  404. [...] a cracker inserted a back-door into the latest downloadable version of the WordPress binary. The tainted binary was available for [...]

    Pingback from lamby :: blog :: WTB signed binaries on March 3, 2007

  405. [...] to a small security problem, we just upgraded to WordPress [...]

    Pingback from Update to 2.1.2 » Sascha Goebels WebLog » Blog Archive on March 3, 2007

  406. [...] Download-Server zu knacken und die Originaldateien durch korrumpierte Versionen zu ersetzen. Ein Update auf 2.1.2 ist zwar ein Klacks (drüberkopieren, upgrade.php aufrufen, fertig) – aber es bleibt doch ein [...]

    Pingback from Notizen » » This is the kind of thing you pray never happens, but it did on March 3, 2007

  407. Actualización de WordPress 2.0.6 a WordPress 2.1.2

    Acabo de actualizar el blog. Tenia una versión bastante vieja, el WordPress 2.0.6. La actualicé a la que salió hace unas horas, la 2.1.2.
    Un cambio que hicieron en los archivos del core que me gustó bastante fue la separación del archivo comment-functi…

    Trackback from GChussir Blog on March 3, 2007

  408. [...] aquí la info completa en el sito de wordpress [...]

    Pingback from Leon » Blog Archive on March 3, 2007

  409. [...] O anúncio oficial você confere aqui. [...]

    Pingback from BlogAjuda » WordPress 2.1.2: atualização de emergência on March 3, 2007

  410. [...] Just passing on the news, and testing the “asides” feature of this theme. link [...]

    Pingback from WordPress 2.1.1 dangerous, upgrade to 2.1.2 now!! at bunnyhero dev on March 3, 2007

  411. [...] Si eres un usuario de WordPress y estás utilizando la versión 2.1.1 es importante que la actualizes a la ùltima versiòn (2.1.2) especialmente si lo haz hecho en estos ùltimos 3-4 días. La razón es que existen fallas en la programaciòn de la seguridad que han sido velozmente aprovechadas por los hackers. Para otros detalles ver el WordPress Blog. [...]

    Pingback from Impesud Technology / WordPress 2.1.1 Users - Important Update on March 3, 2007

  412. [...] If you are using WordPress you must upgrade now! Here is the link  http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Scott Brown » Archive » First post of March! on March 3, 2007

  413. [...] securiteam, confermato sul sito di wordpress. Per ora non aggiungo altro, che vado a cena I commenti [...]

    Pingback from Sicurezza, ICT ed altro » Blog Archive » Backdoor in wordpress? on March 3, 2007

  414. [...] 03/3/2007 Filed under FileVille, Tech, WordPress, Other, Open Source WordPress 2.1.1 has been cracked by a cracker. Everyone should upgrade now to protect their blogs, also if you have a SVN  and [...]

    Pingback from FileVille Blog » Blog Archive » Everyone Upgrade! on March 3, 2007

  415. [...] usan la serie 2.0 no corren riesgo. El asunto es sumamente delicado. Según informa Matt en este post, tuvieron información, a través del correo de seguridad, acerca de un inusual y altamente [...]

    Pingback from Extemp”F”oraneo » Versión 2.1.1 de WordPress altamente peligrosa. Actualizar para evitar problemas on March 3, 2007

  416. [...] ist besonders für all diejenigen interessant, die in den letzten 3-4 Tagen bei wordpress.org das WordPress 2.1.1 Komplett Paket runtergeladen haben und es installiert haben. Ein Angreifer hat [...]

    Pingback from Centurios Blog » WordPress 2.1.2 und der Server Hack on March 3, 2007

  417. [...] Enlaces relacionados: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Martin Aberastegue » Bloggers en peligro - Actualizacion urgente para WordPress 2.1.1 on March 3, 2007

  418. [...] Enlaces relacionados: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Rooter : Bloggers en peligro - Actualizacion urgente para WordPress 2.1.1 on March 3, 2007

  419. [...] Read the official WordPress release here. [...]

    Pingback from One Revolution : Peace Corps / The Gambia : 2.1.1 Compromised: Upgraded to 2.1.2 on March 3, 2007

  420. [...] WordPress yesterday when I built this blog. Thus, this blog is running on 2.1, not 2.1.1. It looks like that was a good move. At least they caught it quickly, but 10 days of backdoored downloads stings a [...]

    Pingback from Oops. WordPress got 0wned. | Nerds of the North Dot Net on March 3, 2007

  421. [...] WordPress Filed Under: Software, Downloads [...]

    Pingback from Nerd Approved - News and Reviews - » WordPress 2.1.1 Hacked, Upgrade Immediately on March 3, 2007

  422. [...] For more details please read this official post from WordPress guys. [...]

    Pingback from Upgrade your wordpress as soon as possible! « ReviewSaurus - The Techie Dino! on March 3, 2007

  423. [...] Si è verificato un accesso non autorizzato in uno dei server di WordPress.org e sono stati compromessi i file di installazione di WordPress. Per non incorrere in inutili rischi [...]

    Pingback from rbnet.it weblog » Archivio blog » Aggiornate subito a WordPress 2.1.2! on March 3, 2007

  424. [...] crap. If you use WordPress 2.1.1 then you need to upgrade to 2.1.2 sharpish ’cause of some lunatic having hacked the files from the download site. Do some [...]

    Pingback from Irreverence is Justified » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  425. [...] jetzt grad rausgekommen ist, dass die Version 2.1.1 meiner Blogsoftware WordPress nach einer Hackattacke mit ein paar Sicherheitslücken gespickt wurde, habe ich soeben die gefixte Version 2.1.2 [...]

    Pingback from Christians Universum » Update fürs Upgrade ... von und mit Christian Tawfik on March 3, 2007

  426. [...] may have read about the recent attack on WordPress release 2.1.1, this did not affected the 1.1.1 release of WordPress MU in any [...]

    Pingback from Development Blog - » Network Upgraded to 1.1.1 on March 3, 2007

  427. [...] Det är lite typiskt det där. Att när man installerar något nytt så är det fel på det… Jag nämnde tidigare att jag uppdaterade motorn bakom den här bloggen. Och nu har det framkommit att nån cracker hade tagit sig in i en server och ändrat programkoden, så alla som laddat ned och installerat just den versionen som jag installerade, hade fått säkerhetsluckor. Så nu har jag fixat det också. WordPress 2.1.2 nu. Läs mer om problemet här. [...]

    Pingback from Östantill 57 » Blog Archive » Säkerhetsluckor och duschdraperi on March 3, 2007

  428. WORDPRESS 2.1.1 HACK: THE REAL LESSON

    Granted, the situation where a malicious hacker managed to modify what was the latest version of WordPress to implant an exploitable security hole is highly unusual, and (one would hope) not likely to happen too often.
    But what should be learned from s…

    Trackback from Population Statistic on March 3, 2007

  429. [...] Als je dus 2.1.1 gebruikt heeft het overwrite van bestanden dus niet veel zin, je moet eerst je oude bestanden verwijderen en daarna de nieuwe uploaden. Lees hier de uitgebreide instructies en uitleg van WordPress zelf. [...]

    Pingback from Netklep - Onze uitlaatklep van het internet » WordPress 2.1.1 veiligheidsrisico`s on March 3, 2007

  430. [...] version 2.1.1 of the popular WordPress blog software was compromised by a hacker who introduced malicious code [...]

    Pingback from Ouch, Another WordPress Update at fredericiana on March 3, 2007

  431. [...] As you may or may not know, a cracker got access to one of the servers that power WordPress.org and inserted some messy stuff. [...]

    Pingback from New Media & IT » WordPress 2.1.1: Upgrade NOW on March 3, 2007

  432. [...] As you may or may not know, a cracker got access to one of the servers that power WordPress.org and inserted some messy stuff. [...]

    Pingback from New Media & IT » WordPress 2.1.1: Upgrade NOW on March 3, 2007

  433. [...] URL: http://wordpress.org/development/2007/03/upgrade-212/  [...]

    Pingback from Dinis Cruz Blog » Blog Archive » Simple Backdoor on WordPress on March 3, 2007

  434. [...] Оф.сайт ВордПресса очень советует обновится до версии 2.1.2 Для тех кто юзает линейку версий 2.0.х обновление не обьязательно, обьязательно лишь для юзеров версий 2.1.х [...]

    Pingback from Александр Мэкаль » Blog Archive » Important: Upgrade to WordPress 2.1.2 on March 3, 2007

  435. [...] word is already out that WordPress 2.1.1 is severely vulnerable and you have to upgrade to WordPress 2.1.2 to keep your blog [...]

    Pingback from Your daily media source » Blog Archive » Upgrading WordPress via Shell on March 3, 2007

  436. [...] Ayer fue lanzada la version de WordPress 2.1.2, despues de que la version 2.1.1 fuera añadida un exploit de Seguridad. [...]

    Pingback from Blackhorn » Disponible WordPress 2.1.2 on March 3, 2007

  437. [...] just upgraded, they discovered a grave security risk. Good thing I just found instructions to upgrade using shell access, which made the whole process a [...]

    Pingback from Multi-faceted Abnormal /blog » Typical on March 3, 2007

  438. [...] You can read more about this at the WordPress site. Posted by DJ Allyn, ITW @ 4:31 pm | | 1 Views [...]

    Pingback from Anti-Idiotarian Rottweiler » Blog Archive » Reported WordPress Exploit on March 3, 2007

  439. WordPress Update: 2.1.2 – Dringend!

    Glücklicherweise hatte ich das Update auf WP 2.1.1 noch nicht durchgeführt! Ein Hoch auf meine Faulheit! Denn heute wurde mitgeteilt, dass sich bei der 2.1.1-Verion eine Sicherheitslücke eingeschlichen hatte:
    Die ganze Geschichte in Kurz…

    Trackback from Ein virtuelles Tagebuch on March 3, 2007

  440. [...] aber trotzdem nicht. “Gelegen” kommt das allerdings mit dem WordPress-Update auf Version 2.1.2. Ein Cracker hatte wohl Zugang zu den WordPress-Servern erlangt und die Version 2.1.1 mit [...]

    Pingback from tikurions Blog » Mondfinsternis? on March 3, 2007

  441. [...] I logged into WordPress this morning there was a very alarming message waiting on the Dashboard: http://wordpress.org/development/2007/03/upgrade-212/ . It appears that a yet as unknown hacker broke into the download servers of WordPress and put some [...]

    Pingback from Andrew Halliday - UK SEO and Web Application Builder » Blog Archive » WordPress Hacked! on March 3, 2007

  442. [...] Alguien logró acceder a los archivos de wordpress y modificó el archivo que estaba para download incluyendo dentro del paquete código malicioso facilmente explotable. Una pena, mala publicidad para un exelente proyecto de Software Libre… Avisan que todos los que se hayan bajado esa versión INMEDIATAMENTE instalen la 2.1.2 [...]

    Pingback from kbglob - tecnologia para geeks, no para tu mamá » WordPress 2.1.1 infiltrado on March 3, 2007

  443. [...] not exactly the headline you like to see when you login to your Dashboard.  On the other hand, I’d prefer to see it on [...]

    Pingback from Rantings and Ravings of an Insane Writer » WordPress 2.1.1 Dangerous; Upgrade to 2.1.2 on March 3, 2007

  444. [...] Dun dun DUUUUUUUUUUUUN. [...]

    Pingback from HDD Killers » Inconvenient To Say The Least on March 3, 2007

  445. [...] security fixes стали появляться с пугающей частотой, так вот новая напасть: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Владимир Яшников » Незамедлительно обновляйте WordPress-блоги on March 3, 2007

  446. [...] it was initially released, WP encourages all users to upgrade to 2.1.2 to patch the security hole.read more | digg story Share this news:These icons link to social bookmarking sites where readers can share [...]

    Pingback from Clickfire Webmaster News » WordPress Server Hacked, 2.1.2 Upgrade Released on March 3, 2007

  447. [...] Matt at WordPress Posted in IT, Breaking News, Tools, Misc, News, Web 2.0, [...]

    Pingback from Bold-Italic-Underline WordPress 2.1.1 has been hacked, advised to upgrade to 2.1.2 « on March 3, 2007

  448. [...] desde el blog oficial de WordPress que en los últimos 3 o 4 días un cracker modificó parte del código de la version 2.1.1 alojada [...]

    Pingback from TechTear :: T_T » Cuidado con WordPress 2.1.1 on March 3, 2007

  449. [...] code was introduced into the WP 2.1.1 download in the last week or so. The dev blog’s got the news. It is recommended to upgrade to 2.1.2. Now! Leave a [...]

    Pingback from bobafred » WP 2.1.2 on March 3, 2007

  450. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Chris Mosby at myITforum.com : WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 3, 2007

  451. [...] Por el tablero de WordPress me he enterado hace unas horas de que los archivos oficiales de la versión 2.1.1. parecen haber sido crackeados por un desaprensivo que ha introducido en ellos código malicioso (más detalles en WordPress 2.1.1 dangerous. Upgrade). [...]

    Pingback from La Bitácora del Tigre · Urgente: actualización de WordPress a la versión 2.1.2 on March 4, 2007

  452. [...] For those curious: Here’s a post with more info about the recent WordPress 2.1.1 vulnerability. [...]

    Pingback from WordPress 2.1.2 - More » Solo Technology on March 4, 2007

  453. [...] you’re using version 2.1.1 on your WordPress blog, beware. Read more about it here. And upgrade to [...]

    Pingback from WordPress Hacked » moneyshotz on March 4, 2007

  454. [...] I’ve also just upgraded to WordPress 2.1.2 after reading about a security vulnerability in 2.1.1, which I had only just finished upgrading.  If you have a WordPress blog, consider doing the upgrade as soon as possible and changing your access passwords. You can read more about the exploit here: WordPress 2.1.2 Upgade [...]

    Pingback from Blog Maintenance | Internet & Affiliate Marketing Demystified | RianBrooklyn.com on March 4, 2007

  455. [...] I’ve also just upgraded to WordPress 2.1.2 after reading about a security vulnerability in 2.1.1, which I had only just finished upgrading.  If you have a WordPress blog, consider doing the upgrade as soon as possible and changing your access passwords. You can read more about the exploit here: WordPress 2.1.2 Upgade [...]

    Pingback from Blog Maintenance | Internet & Affiliate Marketing Demystified | RianBrooklyn.com on March 4, 2007

  456. [...] According to wordpress, If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from Arun’s Blog » Alert: WordPress 2.1.1 hacked. Upgrade to WordPress 2.1.2 on March 4, 2007

  457. [...] you have a 2.1.1 install the sky is about to fall on your head. Upgrade! Upgrade! [...]

    Pingback from Upgrade ASAP to WP 2.1.2 | Fighting to Stay Awake on March 4, 2007

  458. [...] Fonte: WordPress.org [...]

    Pingback from Falha de Segurança: WordPress 2.1.1, Atualize para o 2.1.2 Imediatamente « DropsTech on March 4, 2007

  459. [...] Some creep tried to hack WordPress recently.  If you upgraded to Version 2.1, upgrade again immediately! [...]

    Pingback from RudyCarrera.com - Encyclopaedia Rudaica » WordPress Upgrade on March 4, 2007

  460. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 – If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from holotone.net on March 4, 2007

  461. [...] que Matt indica que hay un gran problema de seguridad en la versión 2.1.1, la noticia tiene 2 historias (explicaciones), una corta y una larga. Long story short: If you downloaded WordPress 2.1.1 within [...]

    Pingback from Un Sanjuanino en Rio Cuarto » Problemas de seguridad en WordPress on March 4, 2007

  462. [...] WordPress is now out in a new version due to a nifty thing; a hacker placed “exploitable code” in the downloadable WordPress-package and presto, people had turned their blog into a box of doom. Not to worry, it’s all patched and tweaked now, but this is just another example of how client-side tech will 0wn your computer/network/life; when the code can be run through your web browser, where’s the security? [...]

    Pingback from Niklas’ blog » Blog Archive » Geeky links: Cowon, Vista, Scrybe, Virtual Ubiquity, Photoshop online, WordPress 0wned on March 4, 2007

  463. [...] all users running WordPress 2.1.1 who have upgraded or installed it in the last week – you need to upgrade to 2.1.2 NOW. A cracker managed to gain access to the WordPress file repositories and swap out some of the [...]

    Pingback from Personal Website of Kieran O’Shea » Serious problems with WordPress 2.1.1 on March 4, 2007

  464. [...] habe ich dann auch fix mal gemacht. Nachdem auf WordPress-Seiten von einem Einbruch auf die Download-Server berichtet wurde und davon, dass Source-Code schadhaft verändert wurde, habe ich fix beschlossen, [...]

    Pingback from Der Blogspion - watching the blogosphere » Blog Archive » WordPress 2.1.1 Dangerous on March 4, 2007

  465. [...] Looks like someone broke into their servers and modified the 2.1.1 download.  News about it here.  “If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a [...]

    Pingback from don’t get hax0r3d :: ultramookie on March 4, 2007

  466. [...] do WordPress sofreu, há cerca de três dias, um ataque malicioso. Alguns arquivos da versão 2.1.1 foram alterados dentro do sistema de downloads oficial das atualizações, para possibilitarem o acesso externo ao [...]

    Pingback from NEWS.Reticencias.Net » Blog Archive » alerta: wordpress 2.1.1 alterado on March 4, 2007

  467. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 (tags: wordpress Security) [...]

    Pingback from 鬼仔’s Blog » links for 2007-03-04 on March 4, 2007

  468. [...] WordPress hacked [...]

    Pingback from Daily Tech Connection » Blog Archive » DTC Podcast #34 Shownotes on March 4, 2007

  469. [...] in den letzten 4 Tagen von wordpress.org das Update auf 2.1.1 heruntergeladen hat, der sollte sofort auf 2.1.2 aktualisieren. Laut des [...]

    Pingback from GreenSmilies.com » Blog Archive » WordPress 2.1.2 erschienen - Die Welt der Smilies ist nicht immer nur gelb! on March 4, 2007

  470. [...] WordPress 2.1.1 is dangerous, upgrade to 2.1.2 immediately. Some malicious code has been injected into the WordPress 2.1.1 code, and an immediate upgrade is urged. Notify all your friends and relatives. [...]

    Pingback from echo “hey, it works” > /dev/null » WordPress 2.1.1 is dangerous, upgrade to 2.1.2 immediately on March 4, 2007

  471. [...] Security Hole Leaves Blogs Wide Open Filed under: Uncategorized — recar @ 2:00 am WordPress 2.1.1 Security Hole Leaves Blogs Wide Open A hacker managed to sneak into the WordPress server and modify the code in the 2.1.1 release, [...]

    Pingback from WordPress 2.1.1 Security Hole Leaves Blogs Wide Open « News Coctail on March 4, 2007

  472. [...] waste time here, go have a look here and upgrade your wordpress [...]

    Pingback from Upgrade WordPress!!! at Chaos’n'Coffee on March 4, 2007

  473. [...] se usi WordPress aggiorna immediatamente alla versione 2.1.2!!! Già che c’eravamo, il Wiki è passato alla versione [...]

    Pingback from Aggiornamenti software at Bzaar on March 4, 2007

  474. [...] dias alcanzo a durar la ultima version de WordPress. El problema es que un hacker logro acceso a los servidores de subversion de las versiones de WordPress, y logro [...]

    Pingback from WordPress 2.1.1 es peligroso at MrAnderson MD on March 4, 2007

  475. [...] More info here. [...]

    Pingback from Critical WordPress Update at yazeez on March 4, 2007

  476. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2: oops [...]

    Pingback from Adminspotting.net » Links for March 03, 2007 on March 4, 2007

  477. [...] just found out about an urgent WordPress release due to a cracker getting into one of the servers and modifying the source code. They added some [...]

    Pingback from Amidst a tangled web » Blog Archive » Urgent WordPress upgrade on March 4, 2007

  478. [...] Reason: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from Upgrade to WordPress 2.1.2 ASAP! | AVINASH - AN IT BLOG on March 4, 2007

  479. [...] WordPress | Upgrade 2.1.2 En openSecurity | Versión 2.1.2 de WordPress [...]

    Pingback from El Blog de Marlex v2.0 » Blog Archive » Cuidado con la Actualización de WordPress 2.1.1 on March 4, 2007

  480. [...] 详细内容见这里   新版下载 推荐: Get Reviewed by this blog for $60 at ReviewMe! [...]

    Pingback from WordPress.org被黑,WP 2.11危险 at 博客报–All about blogging. on March 4, 2007

  481. [...] is a security flaw in WordPress 2.1.1 and I ran into some issues upgrading, that’s why the site has been down [...]

    Pingback from Back Online at Your2Sense.com on March 4, 2007

  482. [...] yesterday there was this announcement.  To save you from having to click the link, here’s the important excerpt: Long story short: [...]

    Pingback from Kelly’s World- A View into the mind of Uber Geek, Kelly Adams » Blog Archive » Timing is everything… on March 4, 2007

  483. [...] WordPress2.1.1发布没到十天就又出更新了,原因是服务器被入侵,有部分代码被修改了,官方的解释在这里,简单的补救办法是下载最新的2.1.2版本全部覆盖。这里的高危版本只是2.1.1,官方说明以前的版本没有此危险存在,仍可以放心使用。至于已更新到2.1.1版本的,需要把博客密码修改下,以免不必要的损失。 [...]

    Pingback from WordPress高危版本–苟世录 on March 4, 2007

  484. [...] official WordPress development blog is reporting that WordPress version 2.1.1 was compromised by a malicious hacker and anyone who downloaded that version in the past several days needs to upgrade immediately to [...]

    Pingback from WordPress 2.1.1 Dangerous, upgrade! on March 4, 2007

  485. [...] official WordPress development blog is reporting that WordPress version 2.1.1 was compromised by a malicious hacker and anyone who downloaded that version in the past several days needs to upgrade immediately to [...]

    Pingback from ExistDifferently.com » Blog Archive » WordPress 2.1.1 Dangerous, upgrade! on March 4, 2007

  486. [...] story short: If you downloaded WordPress 2.1.1 within the past 3-4 days (like I did), your files may include a security exploit that was added by [...]

    Pingback from WordPress 2.11 Dangerous! - Brian Robinson on Marketing on March 4, 2007

  487. [...] What will change for me, is that the blog will no longer need a database to operate and I don’t have to use the silly editor that comes with WP, I’ll just type the posts in any old text editor I like and upload, it’s just that easy with Web2.0. Also I don’t have to worry about following up on the exploits that happen every now and then to popular software, if you’ve got WP in the last few days, upgrade to 2.1.2 right now as it’s been caked. [...]

    Pingback from blogx » Blog Archive » The Guts of Web2.0 on March 4, 2007

  488. [...] MU 开发专用虚拟机 预装软件: WordPress 2.1.1 (直接来自SVN,不受最近的黑客问题影响) + latest SVN version WPMU 1.1.1 + latest SVN version bbPress 0.8.1 + latest SVN [...]

    Pingback from 七十二松工作室 - » Beta测试: WordPress MU开发专用虚拟机 on March 4, 2007

  489. [...] at the rPath wiki page. Included software: WordPress 2.1.1 (directly from SVN, not affected by the recent hacker attack) + latest SVN version WPMU 1.1.1 + latest SVN version bbPress 0.8.1 + latest SVN [...]

    Pingback from 72pines - » Beta release: The Ultimate WordPress MU Virtual Appliance on March 4, 2007

  490. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from dereinzige.de » wordpress 2.1.1 compromittiert on March 4, 2007

  491. [...] La historia completa wordpress 2.1.1 dangerus, upgrade [...]

    Pingback from WordPress 2.1.1 peligroso on March 4, 2007

  492. [...] WordPress released a statement that their download server was cracked and that 2.1.1 versions of their software may contain malicious code inserted by the [...]

    Pingback from sez.so » Blog Archive » botcheck not working after upgrade on March 4, 2007

  493. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 crap. I have two copies of this i need to replace. (tags: wordpress security webdev blog) [...]

    Pingback from ArtLung Blog » Daily Links on March 4, 2007

  494. [...] de ayer con el blog, a última hora de la tarde me dió por echar un vistazo y me encuentro una noticia: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from ThiStrange fruit » Blog Archiv » Upgrading! on March 4, 2007

  495. WordPress 2.1.2

    Rohlala, ces mises à jour ! Yenamarre ! Mais bon, celle-là, apparemment est vraiment nécessaire. En effet, si vous êtes récemment passé à la version 2.1.1, sachez qu’un petit malin a réussi à cracker le serveur de wordpress.org et à mod…

    Trackback from Ma planète on March 4, 2007

  496. [...] From WordPress.org, [...]

    Pingback from Cryptolife: a web blog about, linux, security, privacy, politics and other cool stuff » WordPress.org backdoored on March 4, 2007

  497. [...] Siehe dazu auch [...]

    Pingback from Charles’ Chaos… » Blog Archiv » WordPress-Release ‘# 2.1.1′ Gehackt on March 4, 2007

  498. [...] Looks like some jagoff was out to ruin a good thing. This a-hole got access to one of the WordPress servers and modified the latest version download files with some code that can be executed remotely. They people at WordPress were on it faster than stink of shit and came out with a fix. More can be read about it here. [...]

    Pingback from Pauls Rants and Revelations » Blog Archive » WordPress 2.1.2 Emergency Update on March 4, 2007

  499. [...] important, for those who is on WordPress 2.1.1 you need to upgrade to the latest WordPress version. According to WordPress.org: – Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Upgrade to WordPress version 2.1.2 if you are on version 2.1.1 at Blog . Jiboneus on March 4, 2007

  500. [...] kontrol etmeniz önerilir. Daha fazla bilgi için bu mesajı okuyabilir ve WordPress blogundaki habere [...]

    Pingback from myblog = new Blog(); » Blog Archive » WordPress Remote Code Execution Güvenlik Açığı on March 4, 2007

  501. [...] Statement auf WordPress.org zum Worst-Case [...]

    Pingback from WordPress und der Worst-Case : Googlehupf on March 4, 2007

  502. [...] upgraded or installed to WordPress lately.  Version 2.1.1 has been found to have a security breech.  It seems WordPress has become the new Microsoft – you know you’re doing something [...]

    Pingback from WordPress Security Warning » pacificIT on March 4, 2007

  503. WordPress 2.1.2 released

    Gestern, also keine 2 Wochen nach dem letzten Update, wurde mit der Version 2.1.2 eine neue Version der Blogsoftware “WordPress” (WP) released. Grund für das Updaten war ein erfolgreicher Hack vor ein paar Tagen auf einen der Wordpres…

    Trackback from Dimension 2k on March 4, 2007

  504. [...] ôàéëîâ WordPress è çàñóíóëè â ðàçäàâàåìûå ôàéëû âåðñèè 2.1.1 óÿçâèìîñòü. Òåïåðü WordPress 2.1.1 ñðî÷íî èçûìàþò èç îáîðîòà è íåìåäëåííî íàäî ïåðåõîäèòü ñ ýòîé âåðñèè íà 2.1.2. Òî ëè åù¸ áóäåò ñ Open [...]

    Pingback from WordPress » dxdt.ru: æèâûå çàïèñêè î íåïðàâèëüíûõ ï÷¸ëàõ on March 4, 2007

  505. [...] saab lugeda siit. Uue versiooni saad, nagu alati, [...]

    Pingback from WordPress 2.1.2 - uuenda kindlasti » Aarne bloog on March 4, 2007

  506. [...] che 4-5 giorni fa un cracker sia riuscito ad entrare su uno dei server di wordpress.org e abbia manomesso alcuni files della directory [...]

    Pingback from Levysoft » Aggiornamento critico a WordPress 2.1.2 on March 4, 2007

  507. [...] an excerpt from the WordPress advisory: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from @play » WordPress 2.1.1 hacked, upgrade now on March 4, 2007

  508. [...] My bad karma must not have totally eclipsed my general luck, as the one time I decide not to upgrade immediately to the new version of WordPress is the time that the WordPress download site is hacked and the code modified to include a PHP exploit! [...]

    Pingback from drzy » WordPress hacked on March 4, 2007

  509. [...] that would allow someone to execute remote PHP code on your blogs. Thankfully the guys at WordPress detected this in time and averted a catastophe [...]

    Pingback from Wisetechie Blog : Ctrl your Tech Life » Blog Archive » WordPress 2.1.1 declared Dangerous on March 4, 2007

  510. [...] WordPress alla versione 2.1.2, direttamente dalla 2.1 senza passare dalla 2.1.1 perchè dichiarata pericolosa da wordpress.org, in seguito ad un attacco da parte di un cracker. Il passaggio alla versione 2.1.2 [...]

    Pingback from FABblog » Blog Archive » WordPress 2.1.2 on March 4, 2007

  511. [...] Vier Tage lang lag der virifizierte Download am WordPress Server, wie Robert berichtet. Die Kurzfassung hat die Contentschmiede, die ganze Geschichte gibt’s am WordPress.org Blog. [...]

    Pingback from datenschmutz.net » WP 2.1.x User: Dringend auf 2.1.2 upgraden! - ritchie pettauer schreibt über web 2.0, medien.kultur.technik und objects trouvés im www on March 4, 2007

  512. [...] WordPress 2.1.1 tyvärr blev hackat redan på servern, så uppmanas alla som har den versionen installerad att uppgradera till 2.1.2. Det har vi gjort [...]

    Pingback from kendoka.se » WordPress 2.1.2 on March 4, 2007

  513. [...] I can’t believe it!!! But it’s true. [...]

    Pingback from cat >/dev/null » Blog Archive » wordpress 2.1.1 has been exploited on March 4, 2007

  514. [...] to a security issue in wordpress, the software behind this blog, I upgraded it to the latest (hopefully safe) version. [...]

    Pingback from WordPress security upgrade at log4p on March 4, 2007

  515. [...] hours and I rediscovered the blog, upgraded it to the latest WordPress (fortunately, just after a security fix too) and now to post some [...]

    Pingback from Bones’ Blog of Stuff About Things on March 4, 2007

  516. [...] Eles tiveram um grande trabalho em refazer senhas de usuários, inclusive dos usuários do fórum. O pedido que eles fazem para ajudá-los a contornar todo o problema é repassar essa notícia sugerindo a todos seus amigos que fizeram a migração para a versão 2.1.1, que agora migrassem imediatamente para a versão 2.1.2 conforme sugerido pela notícia no WordPress.org. [...]

    Pingback from Atualização do WordPress 2.1.1 é perigosa » Revolução Etc - Web Standards em uma casca de noz! on March 4, 2007

  517. [...] Bloggmotorn WordPress här på Jonassononline.se är nu uppdaterad till version 2.1.2. Föregående version 2.1.1. innehöll ett allvarligt säkerhetshål, så om du också har en blogg med den versionen, uppdatera geneast. Allt enligt WordPress.org. [...]

    Pingback from Jonasson » Bloggen uppdaterad igen. on March 4, 2007

  518. [...] This site is now running on WordPress 2.1.2. If you’re on 2.1.1, the upgrade is very strongly advised. [...]

    Pingback from sjhoward.co.uk » WordPress 2.1.2 on March 4, 2007

  519. [...] UPDATE: Apparently v2.1.1 has been compromised and it is recommended to upgrade to 2.1.2 quickly. [...]

    Pingback from My Life, My Universe, My Everything » Blog Archive » Upgrade on March 4, 2007

  520. [...] de upgrade te besmetten hoopten ze zo toegang tot andere servers te krijgen. Ondertussen is er een update beschikbaar (versie 2.1.2.) die naast deze security fix ook nog enkele andere updates meegekregen [...]

    Pingback from Unexpected » Blog Archive » WordPress Hacked? on March 4, 2007

  521. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 crack, security, [...]

    Pingback from Blue Forest Blog » Blog Archive » WordPress 2.1.1 Major Security Issue on March 4, 2007

  522. [...] ou 2.1 de WordPress. C’est chose faite, désormais le passage de la version 2.0.4 vers la version 2.1.2 s’est déroule sans trop de difficultés. Cette version, au passage, apporte également un [...]

    Pingback from lbcd78 » Migration de WordPress vers la version 2.1.2 on March 4, 2007

  523. [...] Mas tardaron en liberarlo que en advertir problemas de seguridad y subir una nueva versión. La recien liberada versión 2.1.1 fue crakeada y comprometida su seguridad por lo que hace un par de días fue liberada una nueva versión que ataca este problema. La nota completa esta en la página de wordpress. [...]

    Pingback from DIRECTO AL SUR » Blog Archive » WordPress Crakeado on March 4, 2007

  524. [...] Nota oficial [...]

    Pingback from WordPress 2.1.1 fué hackeada at Alexander Garzon on March 4, 2007

  525. [...] all… All previous posts had to be deleted due to a wordpress exploit. Everything should be fine (for [...]

    Pingback from Talico Great Danes Blog » WordPress Updated on March 4, 2007

  526. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Running WordPress 2.1.1? Upgrade now! | rmay.ca on March 4, 2007

  527. [...] the WordPress within the last 3-4 days, you better upgrade your WP to 2.1.2. Because WordPress reports that someone had accessed their server and modified the download files, so now the 2.1.1 version [...]

    Pingback from AdesBlog.com - Web Technology Related News & Updates on March 4, 2007

  528. [...] (more…) [...]

    Pingback from wehuberconsultingllc.com » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 4, 2007

  529. [...] WordPress Article: WordPress 2.1.1 Dangerous, Upgrade [...]

    Pingback from MalwareTeks Blog : WordPress 2.1.1 User at Risk on March 4, 2007

  530. [...] from : WordPress.org [...]

    Pingback from Update your WordPress blogs now! (for WP v2.1.1) at Never Knows Best on March 4, 2007

  531. [...] check this out http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from Living and loving; autism and deafness » if you have wordpress and just upgraded– on March 4, 2007

  532. [...]   根据WordPress官方博客上的说明,WordPress 2.1.1 dangerous, Upgrade to 2.1.2,由于在三四天前,Wordpress.org的一个服务器被cracker侵入,导致WordPress 2.1.1的压缩包被修改,其中,两个文件内被加入了一些可执行远程PHP的代码,存在很大的安全隐患,因此,WordPress开发组在发布WordPress 2.1.2的同时,敦促大家尽快升级到WordPress 2.1.2,以保证系统的安全。 [...]

    Pingback from 请尽快升级WordPress 2.1.1 | 博客学堂 on March 4, 2007

  533. [...] Gracias a Kriptopoli. Anuncio en WordPress. [...]

    Pingback from Svisor - Seguridad Visor » Archives » Código malicioso en WordPress 2.1.1 on March 4, 2007

  534. [...] able to give Indiscripts a new look plus update it to WordPress 2.1; if you’re running 2.1.1, you must upgrade to 2.1.2! Said version is dangerous. Don’t [...]

    Pingback from Indiscripts » Blog Archive » Indiscripts update on March 4, 2007

  535. [...] Blogging: [Wordpress 2.1.1 is dangerous] [...]

    Pingback from Dario Salvelli’s Blog » Blog Archive » Freshlinks on March 4, 2007

  536. [...] how could this happend. Anyway, this advise comes directly from wordpress.org. March 2, 2007 WordPress 2.1.1 dangerous, Upgrade to 2.1.2 By Matt. Filed under [...]

    Pingback from azwanhadzree.com - » WordPress 2.1.2 on March 4, 2007

  537. [...] Normally I wouldn’t post this, but I know of a few people with brand spanking new WordPress blogs, who went with the 2.1 version of WordPress. Well, if your are using something downloaded within the last few days… Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include… [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 at Standard Mischief on March 4, 2007

  538. [...] Blogs, wikis…, electronic publishing, Blogroll, internet, technology — danicar @ 5:31 pm Please upgrade! Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security [...]

    Pingback from WordPress 2.1.1 is dangerous « Belgrade and Beyond on March 4, 2007

  539. [...] More info [...]

    Pingback from DIYers IT Zone » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 4, 2007

  540. [...] WordPress 2.1.1 dangerous, upgrade to 2.1.2, Sicherheitsmeldung der WordPress-Entwickler [...]

    Pingback from electrobrain » Blog Archive » Achtung Blogger: WordPress-Release bei Server-Hack manipuliert! on March 4, 2007

  541. [...] 2.1.1 fue manipulado Un intruso logró acceder a uno de los servidores de WordPress.org y modificar la versión 2.1.1, de modo que incluyera un [...]

    Pingback from WordPress 2.1.1 fue manipulado « FalconDeOro blog on March 4, 2007

  542. [...] more at the WordPress.org blog, and download the secure version of WordPress here. Leave a [...]

    Pingback from jenn.nu » Blog Archive » Upgrade your WordPress! on March 4, 2007

  543. [...] segundo eles neste post do blog oficial, de uma atualização de suma importância pois, houve uma invasão de hackers em seus [...]

    Pingback from » Alerta de segurança para o WordPress project.47 - Portfolio e blog sobre Web Standards » Arquivo do Blog on March 4, 2007

  544. [...] version 2,12. Tydligen har en bugg kommit in i det som kan ge hackare tillgång till era datorer. Utvecklingsbloggen har mer [...]

    Pingback from Aspiebloggen » Arkiv » Varning för version 2,11 och annonser i bloggen on March 4, 2007

  545. [...] informações no post de aviso no blog da [...]

    Pingback from Matheus Weber da Conceição » Exploit na atualização do WordPress 2.1.1, atualize já! on March 4, 2007

  546. [...] edo eguneratu baduzu, kontuz, segurtasun arazo larri bat izan dezake eta. WordPress-eko kideek azaltzen dutenez, norbaitek beraien zerbitzarian sartzea lortu du eta inor konturatu gabe, WordPress-eko bi [...]

    Pingback from WordPress-Eu » WordPress 2.1.1 bertsioak segurtasun zuloa dauka on March 4, 2007

  547. [...] Źródło: ISC Sans, WordPress. [...]

    Pingback from WordPress ma backdoora » Blog programisty on March 4, 2007

  548. WordPress security update from 2.1.1 to 2.1.2

    Seems that last weeks minor update unfortunately ended in a major update. Somehow someone was able to breach the security on wordpress.orgs download server housing the 2.1.1 files, and put in some malicious code. Two files, wp-includes/theme.php and/or…

    Trackback from Codebox.dk on March 4, 2007

  549. [...] side as this release contains some security patches anyway. You could read the full story here – WordPress 2.1.1 dangerous, Upgrade to 2.1.2. WordPress WordPress NewsShare [...]

    Pingback from Ask Pankaj & Arnab » Blog Archive » Upgrade your WordPress to 2.1.2 on March 4, 2007

  550. [...] side as this release contains some security patches anyway. You could read the full story here – WordPress 2.1.1 dangerous, Upgrade to 2.1.2. WordPress WordPress NewsShare [...]

    Pingback from Ask Pankaj & Arnab » Blog Archive » Upgrade your WordPress to 2.1.2 on March 4, 2007

  551. [...] someone managed to get their nose in where it doesn’t belong on the WordPress servers, and exploit the WordPress 2.1.1 [...]

    Pingback from Eau Salée Lunaire | Mandatory upgrade to WordPress 2.1.2 from 2.1.1, everyone. on March 4, 2007

  552. [...] running 2.1.1 in my test environment.  Good thing I haven’t flicked the switch.  Anyway, here’s the scoop as explained by WordPress: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 [...]

    Pingback from Kim Cameron’s Identity Weblog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 4, 2007

  553. [...] details from [...]

    Pingback from :: Jeff Milner dot Com :: » Blog Archive » WordPress 2.1.1 is “Dangerous” on March 4, 2007

  554. [...] you downloaded WordPress 2.1.1, you likely want to read this advisory and upgrade to 2.1.2 quickly. “This morning we received a note to our security mailing [...]

    Pingback from FreeSoftNews » Blog Archive » WordPress 2.1.1 contained a trojan horse on March 4, 2007

  555. [...] say it happened about 3 or 4 days ago (counting from the time the alert was posted on march 2nd)….ok  WHEW, I downloaded mine well before that (my first post was on Feb 22). They [...]

    Pingback from JonesPC » WordPress users, you might want to upgrade your Wordpres install on March 4, 2007

  556. [...] sedaj je še prišla afera s WordPress 2.1.1, ki je omogočal cross-scripting.  Kar relativno dosti hroščev so našli v PHP-ju v zadnjem [...]

    Pingback from Samirjev blog! » Blog Arhiv » Slabosti PHP-ja on March 4, 2007

  557. [...] To get the details head on over to the WordPress blog. [...]

    Pingback from & Web, Etc. » Blog Archive » WordPress Exploit in Version 2.1.1, Upgrade Immediately on March 4, 2007

  558. [...] To get the details head on over to the WordPress blog. [...]

    Pingback from & Web, Etc. » Blog Archive » WordPress Exploit in Version 2.1.1, Upgrade Immediately on March 4, 2007

  559. [...] hat ja schon die Runde gemacht (z. B. bei Heise oder hier): der wordpress-Server wurde gehakt, also habe ich sicherheitshalber mal die Version 2.1.2 installiert, obwohl die [...]

    Pingback from Randnotizen » Blog Archive » wordpress gehackt on March 4, 2007

  560. [...] WordPress.org: WordPress 2.1.1 a fost aranjat de un cracker Autorii unuia din cele mai populare softuri de blog spun că versiunea disponibilă pentru download a WordPress 2.1.1 a fost aranjată de un cracker, în sensul că include o breşă de securitate. Upgradaţi direct la 2.1.2 (tags: WordPress+2.1.1 crack) [...]

    Pingback from Media lui Comanescu » links for 2007-03-04 on March 4, 2007

  561. [...] seeing the alarming headline “WordPress 2.1.1 Dangerous”, I upgraded to 2.1.2. Painless. Apparently, the WordPress folks got pwned. [...]

    Pingback from reallyboring.net » WordPress 2.1.2 on March 4, 2007

  562. [...] Not all downloads were affected, but it is recommended to upgrade anyway. You can download the latest WordPress files from WordPress.org. Or read more about the update from WordPress.org blog. [...]

    Pingback from WordPress Security Hole 2.1.1 - Niche Marketing on March 4, 2007

  563. [...] WordPress’ quick version of the story… Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, [...]

    Pingback from WebDev101 » Blog Archive » Upgrade to 2.1.2 on March 4, 2007

  564. [...] WordPress 2.1.1 dangerous, upgrade WordPress-Release bei Server-Hack manipuliert [...]

    Pingback from Ich Blog Dich! » Blog Archive » WordPress 2.1.1 kompromitiert on March 4, 2007

  565. [...] Find out more about this here. [...]

    Pingback from » Blog Archive » WordPress security update on March 4, 2007

  566. WordPress 2.1.1 Security Hole Leaves Blogs Wide Open

    A hacker managed to sneak into the WordPress server and modify the code in the 2.1.1 release, introducing an exploit that would allow for remote PHP execution. Although the 2.1.1 package does not seem to have been compromised when it was initially rele…

    Trackback from p0ps blog on March 4, 2007

  567. [...] and modified the files before release. Only WordPress 2.1.1 seems to be affected. Head over to WordPress development blog for further details and update [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 | Live-tr News on March 4, 2007

  568. [...] upgraded to WordPress 2.1.2 quickly after seeing this /. story about an exploit. Here is the story directly from WordPress. Someone inserted malicious code into the distribution. I [...]

    Pingback from Peripatetic Circumambulant » WordPress 2.1.2 on March 4, 2007

  569. [...] Go here for more info WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2: [...]

    Pingback from Yowie’s World » If you have wordpress 2.1.1 installed upgrade to 2.1.2 quickly on March 4, 2007

  570. [...] 2.1.1 has been compromised. Upgrade to 2.1.2. [...]

    Pingback from 2020 Hindsight » WordPress urgent update to 2.1.2 on March 4, 2007

  571. WordPress Security Alert

    Ik las zojuist op de website dat wanneer je versie 2.11 gebruikt van WordPress, je ONMIDDELIJK de 2.12 versie moet downloaden. Het schijnt dat een cracker toegang heeft gekregen tot de servers van WordPress en zodoende enkele files in de downloadpacka…

    Trackback from iplumbing.nl on March 4, 2007

  572. [...] for the people who have downloaded wordpress 2.1.1 few days back, Read this blog from wordpress and make sure you update to 2.1.2 as soon as possible. Incoming Links (via [...]

    Pingback from Online Money Making Sites » Blog Archive » Blog Updated! on March 5, 2007

  573. [...] to Phyl at the Carnival of Healing for yesterday. We had some really BIG problems with our wordpress template, and the whole site was affected for pretty much the whole day [...]

    Pingback from We are back! Sort of.. » Reiki Blogger on March 5, 2007

  574. [...] WordPress users, read this [...]

    Pingback from Simon Speight » WordPress 2.1.1 dangerous, upgrade on March 5, 2007

  575. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 我才升的2.1.1啊…… [...]

    Pingback from 看,那个人在飞! » links for 2007-03-05 on March 5, 2007

  576. [...] (atau beberapa) peretas dicurigai sudah mengubah kode WordPress 2.1.1 dan meninggalkan lubang-lubang keamanan. Ayo, segera upgrade WordPress Anda ke [...]

    Pingback from Priatna · WordPress 2.1.1 Berbahaya on March 5, 2007

  577. [...] morning when I found out that this version of wordpress is dangerous I’m going to upgrade it to 2.1.2 soon. If you find anything unusual or suspicious on this [...]

    Pingback from Archive: WordPress 2.1.1 is dangerous on pria.purnama on March 5, 2007

  578. [...] put some bad code into the 2.1.1 release that allows remote users to do very bad things. So upgrade now… don’t even bother reading the rest of this post just [...]

    Pingback from My N scale blog » Some important WordPress items on March 5, 2007

  579. [...] guess everyone has heard of the recent news on WordPress 2.1.2, which was hurried out of the door because the WP 2.1.1 tarball was somehow altered by a cracker to [...]

    Pingback from Mass Install/Upgrade WordPress with Gentoo+Webapp_config | FuCoder.com on March 5, 2007

  580. [...] Segundo a notificação do WP no seu site, um dos Servidores que hospeda o projeto foi comprometido e um exploit foi adicionado ao [...]

    Pingback from … BlogMind … » Blog Archive » Atualização de Segurança do WP e do Blog on March 5, 2007

  581. [...] of Interest * WordPress bulletin * The Marmot’s Hole * Kimi Ga Yo * New Japanese limits on liquid carry ons * Mimikaki * [...]

    Pingback from Japundit » Japan Talk #060 on March 5, 2007

  582. WordPress 2.1.2

    exploit di wordpress 2.1.1 yg katanya berbahaya

    Trackback from adi's weblog on March 5, 2007

  583. [...] Más información aquí. [...]

    Pingback from Irc Tampico » Blog Archive » Si Estas usando WordPress 2.1.1, actualiza a 2.1.2 cuanto antes on March 5, 2007

  584. Week in Review (25 Feb – 3 Mar 2007)

    No internet at home for over a week now.  Really not coping here!
    Development

    Jeff Atwood laments the quality of programmers, while Phil Haack laments the quality of Jeff’s commenters.
    Long Zeng has a very interesting article on the new Use…

    Trackback from Development on a Shoestring on March 5, 2007

  585. [...] (Vía: Kriptópolis) (Fuente: WordPress.org) [...]

    Pingback from AmarellOcio » Blog Archive » Manipularon la versión 2.1.1 de WordPress on March 5, 2007

  586. [...] Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. More [...]

    Pingback from Mixterr Studio Blog » WordPress 2.1.1 Dangerous, Upgrade 2.1.2 Now! on March 5, 2007

  587. [...] the WordPress development team to label this as a “WordPress 2.1.1 Dangerous, Upgrade” hints at the severity of [...]

    Pingback from WordPress 2.1.2 Emergency Upgrade Released at Andrew Wee | Blogging | Affiliate Marketing | Social Traffic Generation | Internet Marketing on March 5, 2007

  588. [...] hold it right there. I know what you’re going to say. “What about WordPress 2.1.1? It was hacked. It’s a good thing (mt) Media Temple didn’t have that version available!” And [...]

    Pingback from (mt) Media Temple Doesn’t Trust WordPress…? | pomomusings | progressive theology & design on March 5, 2007

  589. [...] noch nicht auf 2.1.2 aktualisiert habt, holt das bitte sofort nach, um sicher zu stellen, dass eure WordPress 2.1 Installation nicht kompromittiert wird. (No Ratings Yet)  Loading [...]

    Pingback from WeblogToolsCollection DE » Blog Archive on March 5, 2007

  590. [...] Ratkaisu: Päivitä ohjelmisto versioon 2.1.2 ohjelmiston julkaisijan ohjeiden mukaisesti. Lisätietoja wordpress.orgista. [...]

    Pingback from » WordPress 2.1.1 päivitettävä - tomstown.pointclark.net on March 5, 2007

  591. [...] Si y actualizaste tu WordPress a la versión 2.1.1 y llevas con ellas instalada desde hace como 5 días, actualizate urgentemente, porque corres peligro. Ya qe parece que algún cracker introdujo una modificación con privilegios de administrador en el SVN de WordPress, añadiendo algunas vulnerabilidades al código. Podemos ver como lo comenta Matt en su bitácora. [...]

    Pingback from Actualizate urgentemente a WordPress 2.1.2 - Bitácora de Ferca Network blog corporativo Ferca Network, registro dominio, alojamiento web, hospedaje web y servidores dedicados linux windows on March 5, 2007

  592. [...] 2.1 to 2.1.1 within a few days after it was released. At least until I read about the entire 2.1.1 release having been compromised to some hacker. Even though I had probably downloaded the new WordPress build before it was [...]

    Pingback from Ellis Web » Upgrading WordPress through Shell on March 5, 2007

  593. [...] 2.1.1 es peligroso Sorprendente que la versión 2.1.1 de Worpress fuera atacada por un intruso, modificando el código de alguno de sus archivos, de modo que [...]

    Pingback from lagateradigital.com :: El Blog » WordPress 2.1.1 es peligroso on March 5, 2007

  594. [...] On a appris pendant le week-end qu’un des serveurs de téléchargement de WordPress avait été piraté et que du coup, la version 2.1.1 avait été aussi piratée… Donc, si vous avez la version 2.1.1, il est impératif pour vous de passer sur la version 2.1.2 ! La version française est en ligne sur le site de WordPress francophone. [...]

    Pingback from Mettez à jour votre blog !! on March 5, 2007

  595. [...] letzten downloadpaket 2.1.1 wurde heimlich fremder code injeziert, details nachzulesen hier. bin ich ja mal froh, dass ich die version erstmal nur zu testzwecken mal nebenan installiert [...]

    Pingback from cracker wordpress manipulation.. - annieone’s weblog on March 5, 2007

  596. [...] engine, WordPress, released version 2.1.1 of their software but now claims that the version was compromised by a cracker. Anyone running WordPress is strongly urged to upgrade to version 2.1.2 immediately. It was [...]

    Pingback from » WordPress 2.1.1 compromised by cracker by FuzzyOpinions.com on March 5, 2007

  597. [...] | unranked Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 [...]

    Pingback from Blogvaria » Upgrade to WP 2.1.2 immediately on March 5, 2007

  598. [...] menggunakan versi 2.1.1 wordpress, eh tadi pagi saya lihat di news feednya wordpress sudah keluar versi 2.1.2. Berita tersebut mengharuskan setiap pengguna versi 2.1.1 untuk update keversi teranyar tersebut. [...]

    Pingback from Sudah Harus Update Lagi « MicoKelana Daily Share on March 5, 2007

  599. [...] ho avuto tempo di scrivere nel week-end. Come molti di voi sapranno, è stata rilasciata in gran fretta la nuova versione 2.1.2 di WordPress, il software che gestisce anche questo blog. La scorsa [...]

    Pingback from Zanblog.it di Giorgio Zanetti » Aggiornare WordPress da 2.1.1 a 2.1.2 on March 5, 2007

  600. [...] der dem Beitrag: “WordPress 2.1.1 dangerous, Upgrade to 2.1.2” ist von einem Hack die Rede der die Versionen von WP 2.1.1 betrifft, wenn man sie in den [...]

    Pingback from WeBlog-WG » Wichtiges WordPress Update! on March 5, 2007

  601. [...] More on this story at WordPress.org. [...]

    Pingback from WordPress 2.1.1 modified by cracker, upgrade to 2.1.2 - rekkerd.org - royalty-free samples, free VST plug-ins, and audio software news on March 5, 2007

  602. [...] è ïîïîðòèë òàì íåêîòîðûå ôàéëû. Ðàçóìååòñÿ, âñå óæå èñïðàâëåíî, íî áåðåæåíîãî Áîã áåðåæåò… Îïèñàíèå [...]

    Pingback from » Îáíîâëÿåì WordPress - óïñ…. » Ïðîñòî Ïóòíèê on March 5, 2007

  603. [...] για εμφάνιση Solaris Telnet Worm- Ενημέρωση ΔΟ WWW για παραβίαση κώδικα των WordPress download servers.- Αποστολή ενημερωτικών μηνυμάτων στα NOCs φορέων [...]

    Pingback from GRNET-CERT Blog » Blog Archive » Απολογισμός ΔΟ CERT 2007-02-26 - 2007-03-04 on March 5, 2007

  604. [...] After setting my new blog with version 2.1.1, I just found out that WordPress had a recent hack attack where some “cracker” as they call it, modified that version package with some code to allow for PHP to run externally. Read all about it here. [...]

    Pingback from Mamurra » WordPress gets violated on March 5, 2007

  605. [...] je recent versie 2.1.1 van WordPress gedownload en geinstalleerd, dan is de kans groot dat je weblog een groot beveiligingslek bevat! Een cracker heeft de source-code op de website van WordPress aan weten te passen, waardoor [...]

    Pingback from Belangrijke WordPress update! : Onbezet.nl on March 5, 2007

  606. [...] From: http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from WordPress 2.1.1 is dangerous at Switch Doctor on March 5, 2007

  607. [...] Find out more about this security update and more by checking out the WordPress Blog [...]

    Pingback from Neo’s Blog » WordPress 2.1.1 Security Update on March 5, 2007

  608. [...] Meldung der Entwickler Download der aktuellen WordPress-Version [...]

    Pingback from » WordPress Update 2.1.1 :: sansegundo.de on March 5, 2007

  609. [...] Se mer info här [...]

    Pingback from Är på väg…. » WordPress backdoor on March 5, 2007

  610. [...] I was investigating upgrading to WordPress 2.1.2 to plug a security issue. The Fantastico Installer currently only offers an upgrade to the flawed 2.1.1 [...]

    Pingback from rolling upgrade » Blog in isolation on March 5, 2007

  611. [...] بحسب تصريح مطور الوورد برس نفسه Matt تعرض أحد مزودات البرنامج الخاص [...]

    Pingback from AbuAnas - مدونتي » اختراق و ثغرة خطيرة لبرنامج WordPress on March 5, 2007

  612. [...] reported on Slashdot and on the WordPress.org blog, the 2.1.1 release of the WordPress blogging system was hacked sometime towards the end of [...]

    Pingback from At the Coalface : A BizTalk Blog » Blog Archive » WordPress Upgrade to 2.1.2 on March 5, 2007

  613. [...] This is because a hacker had managed to gain access to an official WordPress server and altered the download files of 2.1.1 to include some malicious code that could allow them to execute code within your blog installation, possibly taking control over it, steal passwords etc. The full story, and link to the clean version is at WordPress.org. [...]

    Pingback from Upgrade WordPress 2.1.1 to 2.1.2 NOW! » Blog-Op on March 5, 2007

  614. [...]         13:47 | Mrz 05’07 Albtraum für WordPress   Einen Albtraum erlebten die WordPress-Entwickler Anfang des Monats: Ein Hacker hatte sich Zugang zum [...]

    Pingback from » Albtraum für WordPress, Blogpiloten.de - Weblog Update Weekly on March 5, 2007

  615. [...] News at WordPress.org [...]

    Pingback from Damn Crackers! » romantika.name on March 5, 2007

  616. [...] seen on wp-hackers: If you are running 2.1.1, or knows someone who is, I would recommend upgrading to 2.1.2 as soon as p… It is now available at http://wordpress.org/download/ The md5 of the tar.gz is [...]

    Pingback from Peter Westwood » WordPress 2.1.2 released on March 5, 2007

  617. [...] a press release from WordPress we received some questions about the vulnerability of WordPress 2.1.1 which is installed trough [...]

    Pingback from 040 Hosting Blog » Blog Archive » Is Fantastico’s WordPress 2.1.1 vulnerable? on March 5, 2007

  618. [...] Meer informatie Webwereld, WordPress [...]

    Pingback from Bloghelp » Blog Archive » WordPress-software geïnfecteerd na hack site on March 5, 2007

  619. [...] Die lokalisierte deutschsprachige Variante, zu beziehen hier, ist nicht betroffen – es traf die Originalversion des Downloads auf einem wordpress.org-Server. Trotzdem wurde die Version 2.1.1 als gefährlich und [...]

    Pingback from Unikram, Paper, Recherchen & Software » Auch das ist OpenSource on March 5, 2007

  620. [...] Die lokalisierte deutschsprachige Variante, zu beziehen hier, ist nicht betroffen – es traf die Originalversion des Downloads auf einem wordpress.org-Server. Trotzdem wurde die Version 2.1.1 als gefährlich und [...]

    Pingback from Unikram, Paper, Recherchen & Software » Auch das ist OpenSource on March 5, 2007

  621. [...] Die lokalisierte deutschsprachige Variante, zu beziehen hier, ist nicht betroffen – es traf die Originalversion des Downloads auf einem wordpress.org-Server. Trotzdem wurde die Version 2.1.1 als gefährlich und [...]

    Pingback from Unikram, Paper, Recherchen & Software » Auch das ist OpenSource on March 5, 2007

  622. [...] Die lokalisierte deutschsprachige Variante, zu beziehen hier, ist nicht betroffen – es traf die Originalversion des Downloads auf einem wordpress.org-Server. Trotzdem wurde die Version 2.1.1 als gefährlich und [...]

    Pingback from Unikram, Paper, Recherchen & Software » Auch das ist OpenSource on March 5, 2007

  623. [...] WordPress 2.1.1 dangerous, upgrade (WordPress Blog) [...]

    Pingback from Bitelia » WordPress 2.1.2, la versión 2.1.1 fue manipulada on March 5, 2007

  624. [...] być na urlopie, ale takie newsy nie mogły przejść [...]

    Pingback from WordPress - szybka aktualizacja do 2.1.2 at ITblog on March 5, 2007

  625. [...] – there was a security exploit injected into WP 2.1.1 in the last few days. The WordPress team are right on it and have a 2.1.2 upgrade ready to go, [...]

    Pingback from Fantastiblog » Upgrade WordPress to 2.1.2 on March 5, 2007

  626. [...] Server WordPress compromis, codul sursa al versiunii 2.1.1 a fost “imbunatatit” Echipa de la WordPress a anuntat ca pe data de 2.03.2007 , un cracker a obtinut “user privileges” pe unul din serverele WordPress si a compromis codul sursa al versiunii 2.1.1. Alterarea codului sursa a versiunii 2.1.1 consta in introducerea unei posibilitati de PHP remote command execution in fisierele “theme.php” si “feed.php”. Echipa wordpress a fost nevoita sa invalideze si sa declare compromise sursele de la 2.1.1. Pentru cei care au facut saltul la versiunea mai sus mentionata este recomandat sa se treaca la versiunea 2.1.2 a carui cod a fost revizuit si autorizat. Intreaga stire poate fi citita aici. [...]

    Pingback from Server WordPress compromis, codul sursa al versiunii 2.1.1 a fost “imbunatatit” « Aspects of computer security on March 5, 2007

  627. [...] da poco dal blog http://blog.html.it/ oltre che in quello ufficiale di WordPress un cracker sia riuscito ad accedere a uno dei server di WordPress e a manomettere la versione [...]

    Pingback from WordPress Hackers… at IMAGINEPAOLO Web Design Blog - Submit News, Links, SEO Tips, … on March 5, 2007

  628. [...] op draait. Mocht je de afgelopen 4 dagen deze software gedownload of in gebruik genomen hebben – gooi deze dan weg en haal nieuwe [...]

    Pingback from iiMail Weblog » Extragratis spyware op je weblog on March 5, 2007

  629. [...] yaratıcısı Matt Mullenweg tarafından bizzat açıklandığına göre adı bilinmeyen bir cracker wordpress’in download sayfalarına girmiş ve 2.1.1 sürümüne [...]

    Pingback from anilerduran.com | Network ve Server ailesi hakkında yazılarım » Blog Archive » WordPress Hacklendi. on March 5, 2007

  630. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Filed under: Housekeeping [...]

    Pingback from » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 » Supples’ Pub on March 5, 2007

  631. [...] has finally achieved some level of stability – at 2.1.2. The most recent version was found to be dangerous and WordPress developers screamed “upgrade now.” No worries here, though. I rarely upgrade right away because I’ve seen these new [...]

    Pingback from Marcom Blog · Marcomblog Community Update :: PRblogs, Podcasting, Video, Marcom Meme on March 5, 2007

  632. [...] out that someone modified the download of WordPress 2.1.1 from the official servers, so if you’re running it, you might have an exploitable security hole. I upgraded to [...]

    Pingback from Dinhternet » Blog Archive » WordPress 2.1.2 on March 5, 2007

  633. [...] intruso logró acceder a uno de los servidores de WordPress.org y modificar la versión 2.1.1, de modo que incluyera un [...]

    Pingback from el blog de DIMENSIS » WordPress 2.1.1 fue manipulado on March 5, 2007

  634. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from WordPress 2.1.2 *UPDATE* at SCHOCKTHERAPHIE.NET on March 5, 2007

  635. [...] case you haven’t heard, WordPress 2.1.1 has been declared “dangerous” and should be replaced as soon as possible with the newest version, [...]

    Pingback from If you’re using WordPress 2.1.1., upgrade to 2.1.2 as soon as you can - Blogging Expertise - WordPress blog design, installation, and consulting on March 5, 2007

  636. [...] you’re using 2.1.1, please vote, then go upgrade as soon as possible because of this security problem. [...]

    Pingback from The Sunday Poll - On A Monday! » Blog-Op on March 5, 2007

  637. [...] Update on WordPress 2.1.1 Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code […] [...]

    Pingback from AdamH.us » Blog Archive » WordPress Stuff… on March 5, 2007

  638. [...] …pasted source [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 : Mohd Sham Saiman Place on March 5, 2007

  639. [...] WordPress.org here: This morning we received a note to our security mailing address about unusual and highly [...]

    Pingback from BelchSpeak » WordPress 2.1.1 Hacked on March 5, 2007

  640. [...] I decided to take a closer look at the reasons for why I should upgrade to WordPress 2.1.2 and decided that whilst I had in fact upgraded last week, and not within the 3-4 days that the [...]

    Pingback from Have You Upgraded To WordPress 2.1.2 Yet? | Make More Money Blogging on March 5, 2007

  641. [...] by hony on March 5th, 2007 WordPress a avertizat astazi ca versiunea 2.1.1 a software-ului sau a fost compromisa de catre hackeri si recomanda [...]

    Pingback from WordPress - modificat de catre hackeri « bliTz on March 5, 2007

  642. [...] great, now 2.1.1 has been declared dangerous.  Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from The blog of whall » Upgrading my blog software on March 5, 2007

  643. [...] muy bien como, bueno, si lo entiendo, pero me cuesta comprenderlo …  como es posible que la versión 2.1.1. de wordpress  estaba manipulada. Me encuentro con que después de  recuperar hoy mi blog, tengo que ponerme a  actualizar, menudo [...]

    Pingback from » WordPress y 20 minutos | ashet.eu blogeando desde Bilbao on March 5, 2007

  644. [...] you recently upgraded to WordPress 2.1.1 you really need to upgrade to 2.1.2 due to a serious security [...]

    Pingback from WordPress 2.1.1 Vulnerability on March 5, 2007

  645. [...] WordPress 2.1.1 dangerous, upgrade to 2.1.2 [...]

    Pingback from Geekish Things » Blog Archive » Upgrade WordPress on March 5, 2007

  646. [...] Mon 5 Mar 2007 WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Posted by quotes under Security Alert , WordPress.com , WordPress  WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 « Famous Quotes - Famous Sayings on March 5, 2007

  647. [...] Si bajaste wordpress 2.1.1 para utlizar en tu blog debes de actualizar inmediatamente a la versión 2.1.2 mas información en este link. [...]

    Pingback from Tequila 2.0 » Blog Archive » WordPress 2.1.1 es peligroso on March 5, 2007

  648. WordPress 2.1.1 modified from original

    Someone somehow modified some downloads of WordPress 2.1.1, so Matt announced that they’re calling the entire version dangerous. I used to wonder why the 2.0 branch is still maintained at all, considering that 2.1 is out. Perhaps this is part of …

    Trackback from Elliot Lee on March 5, 2007

  649. [...] Un pobrecito hablador nos cuenta: «Acabo de leer en Kriptopolis el articulo WordPress 2.1.1 fue manipulado. Según cuentan en Kriptópolis, un intruso logró acceder a uno de los servidores de WordPress.org y modificar la versión 2.1.1, de modo que incluyera código malicioso fácilmente explotable de forma remota. La “solución” al problema consiste en actualizarse a la versión 2.1.2 cuanto antes. Más información en el sitio de wordpress.» [...]

    Pingback from Cosas de la Red » Blog Archive » WordPress 2.1.1 manipulado on March 5, 2007

  650. WordPress 2.1.1 cracket

    Har du installeret WordPress v. 2.1.1, så gå øjeblikkeligt ind og installér den nyeste version 2.1.2 her.
    Årsagen er, at en cracker tilsyneladende har fået sneget noget kode ind, der giver adgang til din blog/hjemmeside via remote PHP access.
    Wor…

    Trackback from MO/blog on March 5, 2007

  651. [...] stato segnalato sul sito di WordPress un problema verificatosi qualche giorno fa. A quanto pare un cracker sarebbe riuscito a “caricare” sui server una versione modificata della [...]

    Pingback from .:: Securnetwork.net Blog - Massimo Rabbi ::. » WordPress 2.1.2: aggiornare alla nuova versione! on March 5, 2007

  652. [...] 2.1.1 may include security exploit. Avoid it. Upgrade to 2.1.2 [...]

    Pingback from Open Source Skins » WordPress 2.1.1 dangerous on March 5, 2007

  653. [...] http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from WordPress Security Threar 5 March 2007 at The Official Blog of Myles Agnew on March 5, 2007

  654. [...] WordPress 2.1.2: This new version brings new meaning to “security update”. Apparently the integrity of the 2.1.1 download was compromised by a server cracker, leaving hundreds of blogs vulnerable. Immediate upgrading is advised. [...]

    Pingback from Weekly Tech Links » Link Dump 32 on March 5, 2007

  655. [...] If you are running WordPress version 2.1 you’re likely fine, but if you upgraded in the last few days, it’s time to patch a WordPress security hole asap. [...]

    Pingback from » Upgrade Your WordPress Now | An Internet Consultant Speaks | Scott Hendison on March 6, 2007

  656. [...] To read the whole story of this issue, please click here. [...]

    Pingback from baguznet blogs » Blog Archive » Are you WordPress 2.1.1 user? UPGRADE IMMEDIATELY on March 6, 2007

  657. [...] 로그인하면 대쉬보드에 2007년 3월 2일자로 WordPress 2.1.1 dangerous, Upgrade to 2.1.2란 공지문이 떠 있었는데, 영어로 되어 그냥 모르고 있다가 오늘에야 [...]

    Pingback from 무시못할석2의 블로그 » [WP] WordPress.Org 크래킹 on March 6, 2007

  658. [...] For detail cheque to WordPress blog [...]

    Pingback from Update WordPress 2.1.1 ke WordPress 2.1.2 as soon as possible at Blogging on March 6, 2007

  659. [...] WordPress.org web site (here) posted on March 2, 2007 that the 2.1.1 version was hacked and a backdoor added to the code. Users [...]

    Pingback from Tim Weaver : WordPress 2.1.1 May Contain Security Exploit on March 6, 2007

  660. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2[via MetaFilter] [...]

    Pingback from Balaji’s Blog » WordPress build has backdoors built in on March 6, 2007

  661. [...] WordPress.org Technorati Tags: wordpress 2.1.1, wordpress 2.1.2, wordpress compromised, wordpress exploit, [...]

    Pingback from WordPress Download Server Compromised (2.1.1) - Get 2.1.2 NOW! » on March 6, 2007

  662. [...] WordPress › Blog » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. (tags: wordpress security exploit upgrade blogging) [...]

    Pingback from Bieber Labs » links for 2007-03-06 on March 6, 2007

  663. [...] mais na nota oficial divulgada essa [...]

    Pingback from Labpress » Upgrade. WordPress 2.1.2 on March 6, 2007

  664. WordPress Remote Code Execution – Upgrade NOW!

    Over the weekend, there was a notice about a security exploit that was inserted into the install files for WordPress 2.1.1. Care to guess what version of WordPress this blog was running? Don’t worry, I wasn’t about to volunteer that infor…

    Trackback from john-biasi.com on March 6, 2007

  665. [...] that powers this blog, decide to release a security update. Cool. Then some asswipe goes and plants exploitable code in the security update, leaving everyone who upgraded somewhere in the northern regions of Merde Creek sans [...]

    Pingback from WordPress Hiccups (DeepGenre) on March 6, 2007

  666. [...] ooops…2.1.2 [...]

    Pingback from » update WP to 2.1.1 on March 6, 2007

  667. [...] Taking a peek at the site to make sure it was okay, I was surprised to see the public one was running WP 2.0.6 as I thought I had done a 2.1 upgrade… well I had done it on my local test machine, but never got to updating the main site. And a good thing I dawdled since my local copy was the dangerous 2.1.1 version. [...]

    Pingback from A 10 Minute Task That Ate 2 Hours » CogDogBlog on March 6, 2007

  668. [...] a recent update from the WordPress team, which made me quite paranoid, I decided to upgrade my WP installation to [...]

    Pingback from Gormful » Is it still a Monday?! on March 6, 2007

  669. [...] ditinggal begitu saja. hingga akhirnya ada email dari rekan-rekan yang mengatakan bahwa ada bugs di WP 2.1.1 yang diharuskan dan urgent untuk update. . tapi karena penyakit males itu sendiri, yaa email-email [...]

    Pingback from I Made Yanuarta DPY » Blog Archive » Upgrade WP Karena DiHek on March 6, 2007

  670. [...] you downloaded WordPress 2.1.1 your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. For [...]

    Pingback from mihnea docea - the blog » WordPress 2.1.1 upgrades 2.1.2 on March 6, 2007

  671. [...] laziness, my 2.1.1 upgrade has been delayed, though I must say I am lucky for the delay. 2.1.1 was declared dangerous because some hacker got access to the download and injected his own nasty code. Since they [...]

    Pingback from Dimas’s Blog [Beta] » Blog Archive » Minor Updates on March 6, 2007

  672. [...] After nearly three weeks of downtime, the site is back up. The move from my own little blogging tool to WordPress has been relatively painless… There was a small performance issue with 2.1 (which was rather drastic on my 64 meg VM), but the latest patch to 2.1.2 seems to have addressed this, as well as a security exploit. [...]

    Pingback from gregs » Back!! on March 6, 2007

  673. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 — 3 days ago [...]

    Pingback from SQKIKI’s DisneyPlan / Check Your WordPress Version Now on March 6, 2007

  674. [...] dice la pagina sul sito di WordPress, è una di quelle cose che vorresti non succedessero mai… ma è anche una di quelle cose che [...]

    Pingback from Sicurezza, ICT ed altro » Blog Archive » Riguardo a WordPress e alla manomissione del codice on March 6, 2007

  675. [...] and its under the same domain as this blog. The next suggestion was that it could have been the WP 2.1.1 exploit…but I hadn’t install 2.1.1. Anyway I upgraded to 2.1.2 in the hope that it would fix [...]

    Pingback from its always the last thing you try at deanjrobinson.com on March 6, 2007

  676. [...] Mais informações: WordPress [...]

    Pingback from Peopleware » Blog Archive » Ataque ao WordPress 2.1.1!!! on March 6, 2007

  677. [...] se seguridad en la versión 2.1.1 de WordPress Posted marzo 6, 2007 WordPress ha hecho un comunicado acerca de fallos de seguridad en su versión 2.1.1 y recomienda [...]

    Pingback from Fallos se seguridad en la versión 2.1.1 de WordPress « Sistemas Operativos on March 6, 2007

  678. [...] has released a security alert that If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security [...]

    Pingback from WebMantras » Upgrade to WordPress 2.1.2 immediately on March 6, 2007

  679. [...] Read release “WordPress 2.1.1 Dangerous, Upgrade” Share and Enjoy:These icons link to social bookmarking sites where readers can share and discover new web pages. [...]

    Pingback from Template Monster Blog » Blog Archive » WordPress Themes 2.1.1 Dangerous on March 6, 2007

  680. [...] иногда Dashboard читать. Оказывается, недавно выпущенный WordPress 2.1.1 содержит в себе эксплойт, добавленный неизвестным хакером, поэтому [...]

    Pingback from WordPress: Эксплойт в WordPress 2.1.1 - Блог Сергея Третьяка on March 6, 2007

  681. [...] source: http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from bdisfunctional » Blog Archive » WordPress 2.1.1 compromised on March 6, 2007

  682. WordPress : Another security problem….

    It looks like wordpress has hacking problems again… This

    Trackback from Webdigity webmaster forum on March 6, 2007

  683. [...] postingan cak amal beberapa waktu yang lalu wordpress 2.1.1 katanya ada celah disana. Mungkin bagi pemakai wordpress yg blognya dah terkenal pasti was-was, la wong baca titlenya saja [...]

    Pingback from Trashbin of Joko Supriyanto Weblog™ » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on March 6, 2007

  684. [...] as I saw the news in my dashboard, so at least that part is taken care of. Anyway, version 2.1.1 is dangerous, so if you haven’t gotten the new version yet, hop to [...]

    Pingback from Universe » Blog Archive » WordPress 2.1.2. on March 6, 2007

  685. [...] Many of you who follow this site use WordPress.org (downloaded and hosted WordPress). If you are one of them, you need to be aware that WordPress 2.1.1 is dangerous and needs to be upgraded immediately. [...]

    Pingback from WordPress 2.1.1 dangerous, Upgrade to 2.1.2 at effective web ministry notes on March 6, 2007

  686. [...] segnalato su wordpress.org un cracker è riuscito ad entrare su uno dei server di wp.org e ha modificato alcuni files della [...]

    Pingback from WP 2.1.2 at Haboo on March 6, 2007

  687. [...] oh, three seconds after I downloaded WordPress 2.1.1 a new version was released, and the good people at WP insisted we 2.1.1 users upgrade immediately, if not sooner.  I was [...]

    Pingback from Assertagirl » Blog Archive » Because I needed something else to think about. on March 6, 2007

  688. [...] para a versão 2.1.1, que agora migrassem imediatamente para a versão 2.1.2 conforme sugerido pela notícia no WordPress.org. [...]

    Pingback from Inside the Mingo » Atualização do WordPress 2.1.1 é perigosa on March 6, 2007

  689. [...] it seems that the blog software i’m using was hacked a couple days ago. (From the WordPress Blog ) However it only affects those who downloaded the file within the past 3-4 days. Since mine was [...]

    Pingback from cmo’s sanctuary » Blog Archive » WordPress 2.1.1 Hacked on March 6, 2007

  690. [...] it and upgraded in the past couple days, download and install 2.1.2 right away and see the post on the WordPress site for further [...]

    Pingback from Critical WordPress Update! on March 6, 2007

  691. [...] WordPress 2.1.2 was released a few days ago. There were potential issues with 2.1.1 depending on when you obtained the download. To be safe, 2.1.1 in its entirety has been deemed dangerous. If you are running that version, you should upgrade to 2.1.2. Get the latest version of WordPress here. For more information on the specifics, check here. [...]

    Pingback from StickiWidgets » Blog Archive » WordPress 2.1.2 Update and WP-Cache Plugin on March 6, 2007

  692. [...] Explicación “larga” y bastante más técnica que la mía de lo sucedido (en inglés) [...]

    Pingback from LordMaX Blog » Que no panda el cúnico… on March 7, 2007

  693. [...] 更新:還是不要太拼才好,WordPress 2.1.1 被黑了,而且十天後才被發現,呼呼,這下刺激了 [...]

    Pingback from Arthur Hsu’s Blogz » Blog Archive » 愛拼才會贏 on March 7, 2007

  694. [...] For more explanation, refer to WordPress http://wordpress.org/development/2007/03/upgrade-21 [...]

    Pingback from Internet Strategy Blog - WordPress 2.1.1 Dangerous on March 7, 2007

  695. [...] For further info, visit here. [...]

    Pingback from SquareCookies » Danger: WordPress 2.1.1 on March 7, 2007

  696. [...] to WordPress 2.1.2. A must as the 2.1.1 was [...]

    Pingback from Nuuska » Updated to WP 2.1.2 on March 7, 2007

  697. [...] xbox360Chi ha aggiornato ultimamente WordPress è vivamente invitato a passare urgentemente alla versione 2.1.2. Secondo Secunia il problema dell’ultimo aggiornamento di WordPress 2.1.1 è giudicato [...]

    Pingback from undolog » Blog Archive » Bollettino sicurezza: WordPress e XBox 360 on March 7, 2007

  698. [...] boy. They messed up big time. The good folks at WordPress discovered that some 2.1.1 releases contained a trojan horse added by a cracker. Consequently, they prepared a new release, 2.1.2, which also has some minor [...]

    Pingback from The Grey Shadow » Stop the Presses: WordPress 2.1.1 Dangerous, Upgrade Immediately to 2.1.2! on March 7, 2007

  699. [...] WordPress(个人版)又更新了。最新版是2.1.2,并被明确告知2.1.1是“危险的”: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. [...]

    Pingback from WordPress升级到2.1.2,你是不是有点烦? - The Dev Log on March 7, 2007

  700. [...] should upgrade or immediately prevent access to certain queries to prevent an attack described here. If the server is running Apache with mod_security, simply update your httpd.conf with the [...]

    Pingback from mod_security rules to prevent WordPress 2.1.1 attack at fak3r on March 7, 2007

  701. [...] running WordPress should be aware of the recent security breach at WordPress HQ, that caused a pretty troubling “tainting” of the 2.1.1 release [...]

    Pingback from Red Sweater Blog - My Super Ex-Wordpress on March 7, 2007

  702. [...] The WordPress trio have been upgraded to version 2.1.2. Nobody ever reports bugs, so I will not ask for [...]

    Pingback from a sibilant intake of breath » Blog Archive » M.Phil teaching complete on March 7, 2007

  703. [...] de segurança. Recomenda-se que todos os que tenham o update anterior, que o alterem por este novo patch. Nós [...]

    Pingback from friiki bizz » Archive » WordPress com Problemas on March 7, 2007

  704. [...] WordPress 2.1.2 Blog Link Participate! Leave your comment. [...]

    Pingback from Updated to WordPress 2.1.2 @ The Flishtorium Blog on March 7, 2007

  705. WordPress violato

    Se avete appena installato il vostro nuovo blog WordPress 2.1.1, oppure avete da pochi giorni aggiornato, allora procuratevi all’istante l’ultima versione 2.1.2 onde evitare spiacevoli inconvenienti.
    Il sito di WordPress è stato violato. De…

    Trackback from Il tuttlog di Tassoman on March 7, 2007

  706. [...] downloaded recently), you need to upgrade your installation because of a security exploit that made its way into the [...]

    Pingback from developercast.com » Blog Archive » Community News: WordPress 2.1.1 Dangerous, Upgrade on March 7, 2007

  707. [...] pretty bad security exploit was included in WordPress 2.1.1. If you have this version installed you’re strongly encouraged to upgrade as soon as [...]

    Pingback from Unofficial DreamHost Blog » Blog Archive » Security Issues on March 7, 2007

  708. [...] GfxDizayn‘ında belirttiği gibi hackerlar WordPress ile uğraşıyor. WordPress ard arda iki sürüm birden çıkardı son olarak WordPress2.1.2 deyin. Link [...]

    Pingback from Fatih Hayrioğlu’nun not defteri » 7 Mart 2007 Web’den seçme haberler on March 7, 2007

  709. [...] http://wordpress.org/development/2007/03/upgrade-212/  [...]

    Pingback from CommaVee » Blog Archive » Upgrade WordPress now on March 7, 2007

  710. [...] a week ago, WordPress announced that they had suffered a break in to one of their servers by a hacker. This hacker compromised [...]

    Pingback from Security Alert: WordPress 2.1.2 on March 7, 2007

  711. [...] to the Herald: As was reported last week, the latest upgrade of WordPress was attacked from a server breach and everyone was incredibly helpful in spreading the world that a new replacement and updated (and [...]

    Pingback from drivebyshooter.net » Blog Archive » WordPress 2.1.2 is a mandatory upgrade on March 8, 2007

  712. [...] case you missed it, wordpress.org got hacked. This is the final straw for me. I’ve been growing more and more dissatisifed with wordpress [...]

    Pingback from andrew carter - Bye Bye, WordPress on March 8, 2007

  713. [...] from this report came from http://wordpress.org/development/2007/03/upgrade-212/ by Matt and to wit: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, [...]

    Pingback from Unwritten Thoughts WordPress 2.1.1 exploited! « on March 8, 2007

  714. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from Security Exploit: Upgrade Your WordPress 2.1 Immediately! : PHOTOlulu - Enjoy The View. on March 8, 2007

  715. [...] I didn’t go from WordPress 2.1 “Ella” to 2.1.1 though, because it looks like a cracker penetrated their site (WordPress’s, not Dreamhost) and changed the source code. The code allows a PHP code [...]

    Pingback from He had a lot to say. He had a lot of nothing to say. » Second post in one day on March 8, 2007

  716. [...] This is obviously a serious issue for WordPress, but in fairness they appear to have responded in the right way, publicising the attack and doing everything possible to make sure it doesn’t happen again. http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from WordPress Hacked « Not Rocket Science on March 8, 2007

  717. [...] zu modifizieren. Die so veränderte Software erlaubte die externe Ausführung von PHP-Code. Bekannt wurde die Sicherheitslücke bereits am 02.03.2007. Selbiger Artikel in deutscher Sprache war am [...]

    Pingback from Update WordPress 2.1.1 auf 2.1.2 - mobelogged life ... on March 8, 2007

  718. [...] WordPress 2.1.1 dangerous, upgrade [...]

    Pingback from jung.eu » WordPress cracked… on March 8, 2007

  719. [...] explications se trouvent ici et les instructions de mise à jour ici (notez cette phrase importante : Important: when upgrading [...]

    Pingback from blorgoz » Faille de sécurité dans WordPress 2.1.1 on March 8, 2007

  720. [...] 更新が滞っていたが、その間にも近所の新しい分譲住宅地で地主が首を吊ったとか、WordPressのサーバがクラックされて配布中のファイルが書き換えられていたりとか、まあいろいろとあった。あと、誕生日も過ぎた。 [...]

    Pingback from Selfkleptomaniac » Blog Archive » 日々雑感 on March 8, 2007

  721. [...] WordPress 2.1.1. Dangerous, Upgrade Wer Ende Februar / Anfang März Version 2.1.1. von WordPress heruntergeladen hat, könnte eine gefälschte Variante des Scripts erhalten haben. Ein Hacker hat auf den Download-Servern von WordPress eine Version mit einer eingebauten Sicherheitslücke eingeschleußt. Es wird angeraten, das Update zu Version 2.1.2 einzuspielen [...]

    Pingback from blog.deobald.org » Blog Archive » Quergelesen 2007-03-08 on March 8, 2007

  722. [...] you installed WordPress 2.1.1 you may be at risk for an exploit, according to Matt Mullenweg: Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may [...]

    Pingback from Upgrade to WordPress 2.1.2 (this is not optional) | Chris Webb: Publishing, Media, and Technology on March 8, 2007

  723. [...] And I suggest you do the same. Of course, this is a bunch of dribble as I test my installation, but it really is a good idea. Especially if you just upgraded to 2.1.1 a few days ago. [...]

    Pingback from One man’s voice » Upgraded to WordPress 2.1.2 on March 8, 2007

  724. [...] 长话短说怎么讲?Long story short,没冠词,没动词,就是这么说。 [...]

    Pingback from 英语难学么? - 在路上 on March 9, 2007

  725. [...] after reading this post, on WordPress.org, I decided that it would be smart to upgrade to 2.1.2.  So far, I am very [...]

    Pingback from USNPODCAST.COM » Upgrade on March 9, 2007

  726. [...] people who make WordPress (which powers this and many other blogs) reported a frightening breech of security. To summarize; if you have WordPress version 2.1.1, upgrade immediately. Tell your friends. [...]

    Pingback from Liberaltarian » WordPress Security Breech on March 9, 2007

  727. [...] in other news: Upgraded the site again. Some security issue that I’m probably not even affected by, but I figured, eh, too nerdy not to do it. posted [...]

    Pingback from Polikua » PEPFAR on March 9, 2007

  728. [...] cracker got into WP’s systems and compromised the release. A new release was put out to protect against this since all of the files are now suspect. Upgrade [...]

    Pingback from HCS’s and Gen’s Place » Blog Archive » Upgrade WordPress now! on March 9, 2007

  729. [...] more at http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from yozora.org » WordPress 2.1.1 Compromised on March 9, 2007

  730. [...] Per questo abbiamo scelto come piattaforma WordPress 2.1.2 (se pensi di essere al passo con la 2.1.1, meglio aggiornarla: c’è una falla pericolosa). [...]

    Pingback from Il backstage di Beanbol at Beanbol on March 9, 2007

  731. [...] trojan yerleþtirdiler. WordPress’in kurucusu Matt Mullenweg, 2.1.1 sürümünü indirenleri color=#0000ffkendi blog sayfasýndan uyararak indirilen dosyalarýn güvenlik açýklarýnýn bulunduðunu iletti ve acilen 2.1.2 sürümüne [...]

    Pingback from Bilgisayar korsanlarý WordPress’e sýzdý - Beþiktaþ Forum ( 1903 - 2007 ) Taraftarýn Sesi !. on March 9, 2007

  732. [...] think I’m ready to upgrade to WordPress 2.1.2, just have to find the hours to do [...]

    Pingback from A View from Home » So much to blog about, so little time on March 9, 2007

  733. [...] das Update auf WordPress 2.1.2 gewagt Scheint alles so zu laufen wie es soll. Nach einem Datenbank- und Dateien-Backup habe ich [...]

    Pingback from Update auf WordPress 2.1.2 at ogeeBloggin’ on March 10, 2007

  734. [...] news] WordPress.org has announced that some of the 2.1.1 packages have been backdoored. Code has been added to (at least) feed.php [...]

    Pingback from hiredhacker.com » Blog Archive » Some WordPress 2.1.1 packages are backdoored. on March 10, 2007

  735. [...] in with a stable version, 2.1.2, I’m going to be upgrading all their blogs this weekend. See WordPress 2.1.1 dangerous, Upgrade to 2.1.2. Not to worry, I haven’t upgraded those blogs recently as it always seems wise to wait until [...]

    Pingback from infOpinions? · Good Reading :: Interesting Links for the Week on March 10, 2007

  736. [...] think I’ve upgraded to 2.1.2 – a security update to [...]

    Pingback from Really Bad Eggs » WordPress Roundup on March 10, 2007

  737. [...] I finally upgraded to WordPress 2.1, which was soon followed by 2.1.1, which was hacked and infected, and then upgraded to 2.1.2. Version 2.1 seems fine, and I’ll sit out the next few minor upgrades [...]

    Pingback from » Blog Archive » WordPress upgrade, SEO tactics, site stats, and other kinds of geekery on March 11, 2007

  738. [...] I have tested Scripturizer 1.7 on WP 2.1.2, and it appears to be working well. Please let me know if you run into any snags. (I do not recommend using WP 2.1 due to the security breach….) [...]

    Pingback from Scripturizer 1.7 Beta « Scripturizer Plugin Development on March 11, 2007

  739. 部落格更動記事20070312

    要睡覺了,把今天對blog做的更動記錄一下好了,以免忘記。

    升級到Wordpress 2.1.2。
    因為我看到的時候,2.1.1已經被發現有問題,所以2.1.2已經釋出,所以直接從2.0升級到2.1.2。升級不見得是好…

    Trackback from 抬起尊臀去敲門 on March 11, 2007

  740. [...] den neusten Stand gebracht. Wobei es sich ja noch als glücklicher Zufall herausstellte, dass ich 2.1.1 aus Zeitgründen(=Faulheit) übersprungen habe. Diese ganze Geschichte erinnert mich an die [...]

    Pingback from blog-apoc : Blog Archive : Gemischtes on March 11, 2007

  741. [...] aflat din stirile WordPress ca versiunea 2.1.1 a fost grav afectata de un atac deosebit. Se pare ca un utilizator cu drept de [...]

    Pingback from » WordPress 2.1.1 - pericol major( kindablog ) on March 11, 2007

  742. WordPress2.1.2

    Err, I just couldn’t think of a subject. I hadn’t updated my blog in a long time and the reason why I chose this subject is because when I entered my wordpress dashboard, it said
    WordPress 2.1.1 dangerous, Upgrade to 2.1.2 — 5 days ago.
    M…

    Trackback from Swap's Blog on March 12, 2007

  743. [...] despite a couple of recent security issues, is clean, easy to customize, and intuitive. If you’re experienced with MySQL and PHP, it [...]

    Pingback from TreyPerry.com » Blog Archive » Funny I Should Say on March 12, 2007

  744. [...] Yes that is right! Where was I? How did I miss this news? I was about 10 days late before I know that somebody, they called him/her “the cracker” had gain accessed to one of the WordPress servers and did something to the original 2.1.1 download file. Read the complete story here. [...]

    Pingback from » Where Was I? noomansblog: on March 12, 2007

  745. [...] meer spannende verhalen over gehackte wordpressreleases mag je hier verder lezen. Besteed je jou tijd liever wat nuttiger dan kun je vanaf nu constant op F5 [...]

    Pingback from Thijs in Finland » Blog Archive » Upgrade WordPress 2.1.2 on March 12, 2007

  746. [...] just upgraded my blog software reading this post on the WordPress development blog from March 2, 2007 If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security [...]

    Pingback from WordPress 2.1.1 Dangerous, Upgrade | Ken H. Judy on March 12, 2007

  747. [...] Mas informacion, en este post de WordPress.org [...]

    Pingback from Masio IT » Blog Archive » Actualiza _YA_ a WordPress 2.1.2 on March 13, 2007

  748. [...] 2.1.2 Mandatory Upgrade: This is a reminder of the server breach of the latest version of WordPress and announcement that the latest version of WordPress is a [...]

    Pingback from WordPress Wednesday: Mandatory Update Reminder, WordCamp2007, Instant Upgrade Plugin, SxSW Conference, and More at The Blog Herald on March 14, 2007

  749. [...] En cuanto al sospechoso habitual de WordPress, la verdad es que ultimamente han tenido demasiados “errores”, y realmente el más reciente me ha hecho pensar en buscar alternativas. [...]

    Pingback from Que usar para un nuevo Blog? en EGG Blog on March 15, 2007

  750. [...] to a security exploit in version 2.1.1 of wordpress we have to do an important upgrade shortly. Consequently, our initial [...]

    Pingback from Fashioning Mauritius » Blog Archive » Upgrade on March 15, 2007

  751. [...] nun ohne Probleme durch. Glücklicherweise hab ich damit ein wenig länger gewartet und nicht die gecrackte Version installiert. Happy [...]

    Pingback from leo34.net » Blog Archive » Update von WordPress 2.0.x auf 2.1.2 on March 15, 2007

  752. [...] Quellen: WordPress.de ( “Worst Case“, “2.1.2“), WordPress.org. [...]

    Pingback from WordPress, Oh WordPress! » BODY-SNATCHER’s Blog on March 15, 2007

  753. [...] WordPressin tiedote [...]

    Pingback from Niitä ja näitä » WordPress 2.1.1:ssä vakava tietoturva-aukko on March 16, 2007

  754. [...] If you are running version 2.1.1 – you are encourage to upgrade now due to a pretty major security issue. Technorati Tags: upgrade, wordpress You can also bookmark this on del.icio.us or check the [...]

    Pingback from Zack Rippy » WordPress 2.1.2 Upgrade on March 16, 2007

  755. [...] it might be a good idea to upgrade to the latest beast.  I did some reading and lo, I find this; http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from RandomStringOfWords » WordPress Upgrade Woes on March 16, 2007

  756. [...] code was added to version 2.1.1 which allowed remote PHP code execution. You can read more here. Anyway, I have updated to version 2.1.2 and deleted all my files and updated all the files from my [...]

    Pingback from securitytechscience.com » Blog Archive » Let’s 0wn my Web Server on March 17, 2007

  757. [...] you can see ths, I successfully have upgraded the blog to WordPress 2.1.2. At some time, I’ll write something with some content, but not now…. Filed under: [...]

    Pingback from Read This Blog! » Upgraded to 2.1.2 on March 17, 2007

  758. [...] I’ve finally upgraded from my original installation of WordPress 1.5.2 to WordPress 2.1.2, mainly to take advantage of the Akismet spam catcher. I’ve been getting 3 dozen spam comments a day, which I’ve had to manually delete, but hopefully I won’t see any more spam now. I was going to upgrade earlier, to WordPress 2.1.1, but my procrastination has paid off, because a hacker broke into the WordPress download site and added a back door to that version. [...]

    Pingback from Mark Staples » Upgrade to WordPress 2.1.2 on March 18, 2007

  759. [...] If you’re running Word Press version 2.1.1, you need to upgrade right away! Word Press has declared the entire version dangerous. [...]

    Pingback from The Big Word Press Upgrade | The Daily Twaddle on March 19, 2007

  760. [...] Uma das ferramentas mais práticas e populares para a publicação de conteúdo em sites e blogs, a WordPress foi vítima de um ataque que resultou por vários dias na oferta de download do programa com um [...]

    Pingback from Hackers inserem spyware no WordPress « O diário da informática on March 19, 2007

  761. [...] files – the new versions in the last time had too often little problems and one of them had an exploit [...]

    Pingback from bensKnowledgeBlog - mooh.it » i am thinking of switching from wordpress to serendipity on March 19, 2007

  762. [...] in case anyone with a WordPress blog stops by, you need to know that version 2.1.1 was officially declared Dangerous by WordPress developers. Head over to the official WordPress site for details, and a clean download to upgrade to a safe [...]

    Pingback from WordPress is Dangerous - Almost Exciting! on March 19, 2007

  763. [...] Show notes: WordPress blog security exploit [...]

    Pingback from Beyond !nnovation Podcasts » Blog Archive » HakSploit ep 1×06 on March 20, 2007

  764. [...] WordPress 2.1.1 compromised, update to 2.1.2 [...]

    Pingback from The WordPress Podcast · Episode 20: WordPress 2.1.1 Contains Some Bad Mojo! on March 20, 2007

  765. [...] vom 2. + 3.3.2007 Die Sicherheitsprobleme bei WordPress dauern [...]

    Pingback from WordPress Sicherheitsprobleme « WLAN Weblog on March 20, 2007

  766. [...] more over this exploit at the wordpress website Filed under algemeen, web, wordpress having Leave a [...]

    Pingback from Dichtlog » Blog Archive » WordPress 2.1.1 on March 20, 2007

  767. [...] Read more » This entry was posted on Monday, March 19th, 2007 at 1:34 pm and is filed under Software. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. [...]

    Pingback from Notebook » Blog Archive » A danger of open-source development… on March 20, 2007

  768. [...] and exploits, I promise you’ll learn a thing or two.. Another spicy piece of news is the backdoored WordPress systems (v2.1.1) story, occurred earlier this month. that one really made m laugh [...]

    Pingback from Recognize-Security March 2007 on March 27, 2007

  769. [...] an update to the systems issue we had last month, we have taken dozens of additional precautions with the servers and systems that run WordPress.org [...]

    Pingback from WordPress 2.1.3 and 2.0.10 on April 4, 2007

  770. Migrating from WordPress to Movable Type (Part 1)

    No, that’s not backwards. My three-month experiment was an unexpected failure. While WordPress is easy to install, feels very slick and has some innovative features (especially with Ajax plugins), there have been enough serious problems that I have go…

    Trackback from Jim Carson on April 5, 2007

  771. [...] an update to the systems issue we had last month, we have taken dozens of additional precautions with the servers and systems that run WordPress.org [...]

    Pingback from » Blog Archive » Nerd Alert on May 16, 2007

  772. WordPress DevTeam declares WP v.2.1.1 ‘dangerous’

    In fact, the developers went so far as to explain that although not all downloads of [version] 2.1.1 were affected, we’re declaring the entire version dangerous.

    Trackback from Scoop's Views on June 29, 2007

  773. WordPress 2.1.1 Vulnerable

    Este post fue agregado a teknear.com para su votación. Votalo!

    Trackback from www.teknear.com on September 17, 2007

  774. [...] you think this scenario is too unrealistic? It’s already happened on a large scale on WordPress 2.1.1 (although no damage really [...]

    Pingback from Readers Behaving Badly - The WordPress Joe Job » Reader Appreciation Project on September 24, 2007

  775. [...] Backdoored Version (more) [...]

    Pingback from BlogSecurity » WordPress BlogWatch on September 25, 2007

  776. [...] WordPress Backdoor checks (see WP) [...]

    Pingback from BlogSecurity » wp-scanner 1.3b released on October 4, 2007

  777. [...] Published March 3rd, 2007 Celebrities , WordPress To my luck, there’s a security flaw in WordPress 2.1.1 so I [...]

    Pingback from Upgrade! « Anything Goes on October 5, 2007

  778. [...] WordPress Backdoor 檢查(給 2.1.1 那個安全性漏洞用)。 [...]

    Pingback from WordPress Scanner 1.3 Beta 服務 « Kirin Lin on October 8, 2007

  779. [...] như thông báo của nhóm phát triển wordpress thì: Long story short: If you downloaded WordPress 2.1.1 [...]

    Pingback from An Sinh’s blog » WordPress 2.1.1 dangerous! on October 11, 2007

  780. [...] Enlaces relacionados: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 http://wordpress.org/development/2007/03/upgrade-212/ [...]

    Pingback from PHPes.net - PHP en Español » Actualizacion urgente para WordPress 2.1.1 on November 9, 2007

  781. [...] an update to the systems issue we had last month, we have taken dozens of additional precautions with the servers and systems that run WordPress.org [...]

    Pingback from 默默の丸 » Blog Archive » WordPress 2.1.3 and 2.0.10 on November 22, 2007

  782. [...] just saw this. i guess i need to upgrade again. Posted in [...]

    Pingback from ellipsis… » Blog Archive » lost it all… again. on November 24, 2007

  783. WordPress 2.1.2

    Just a short while after upgrading WordPress to 2.1.1 there’s an announcement that 2.1.2 is released, with a warning that everyone running the older version upgrade immediately due to a potential security exploit. Go on, do it. Now. Do not pass g…

    Trackback from Here, Now on December 15, 2007

  784. WordPress 2.1.2

    Just a short while after upgrading WordPress to 2.1.1 there’s an announcement that 2.1.2 is released, with a warning that everyone running the older version upgrade immediately due to a potential security exploit. Go on, do it. Now. Do not pass g…

    Trackback from Here, Now on December 15, 2007

  785. [...] that opens its users to abuse from third-parties). A few days ago it was SquirrelMail, in March it was the massively extended WordPress blogging [...]

    Pingback from Open source projects, compromised — Subreption blog on December 16, 2007

  786. [...] like another time procrastination paid off as I had not updated yet! You can read about the issue here. Posted by jtadlock Filed in IT, [...]

    Pingback from WordPress 2.1.1 Issues « Jtadlock’s Weblog on December 27, 2007

  787. [...] knew there was a security upgrade in one of those versions I skipped, but with new versions coming out every week, I really became [...]

    Pingback from How My Blog Got Hacked | Stephan Miller on January 15, 2008

  788. [...] cargar y utilizar). Para probar una última cosa, y sabiendo que el WP 2.1.1 había tenido algunos “problemas” con un cracker, me decidí a hacer un upgrade al WP 2.1.2, cosa que siguiendo los pasos que se indican en la [...]

    Pingback from Letras en Libertad » WYSIWYG! on January 21, 2008

  789. [...] Apa yang harus dilakukan? Jika anda mendownload wp-2.1.1 dalam rentang tanggal 27-februari sampai 2 Maret, segera update wordpress anda ke versi wp-2.1.2. Berita selengkapnya silakan baca di situs wordpress. [...]

    Pingback from Buat ngingetin : wp-2.1.2. ke hack.. what should U do.. « Noiska golbeW on January 23, 2008

  790. [...] Trojan no WordPress (tags: virus antivirus wordpress trojan horse) [...]

    Pingback from links for 2008-01-24 « Ronaldo Folgazão Richieri on January 24, 2008

  791. [...] I was investigating upgrading to WordPress 2.1.2 to plug a security issue. The Fantastico Installer currently only offers an upgrade to the flawed 2.1.1 [...]

    Pingback from rolling upgrade - My Habari on February 2, 2008

  792. [...] Read more [...]

    Pingback from Health Blog » Blog Archive » Warning to WordPress 2.1.1 Users on February 9, 2008

  793. [...] would like to respond to that by pointing out that wordpress.org was breached in March of 2007, and that the download zip of 2.1.1 offerred on that site was modified. In sharp contrast, my site, [...]

    Pingback from village-idiot.org -- WordPress forum notes on February 20, 2008

  794. [...] poco más de una hora Matt (desarrollador de WordPress) ha informado de código malicioso en WordPress 2.1.1. Recomienda actualizar URGENTEMENTE a la nueva versión [...]

    Pingback from ¡Actualización URGENTE a WordPress 2.1.2! | JaimeBlanco.Com on February 24, 2008

  795. [...] “Wordpress 2.1.1 tehlikelidir, yükseltin” başlığı, aklima hackerların wordpress’i fena kafaya taktıkları ihtimalini getirdi. Güya bir cracker! wordpress 2.1.1 dosyalarını ellemiş! ve hemen 2.1.2′e yükseltmeniz gerekiyormuş. Birisi bu cracker arkadaşı çok kızdırmış olmalı! ki wordpress geliştiricileri, haftada bir güncellemek zorunda kalıyorlar. Download sayfasının başlığında, nedense 2.1.1 yazıyor hala… Biz yinede, güncellemekten ziyade, dosya yedeklerini alalım. Ola ki bir hafta gecikirsek! cracker arkadaşa çarpılmayalım. [...]

    Pingback from Ahmet Eren TURAN - Tasarım ve Teknoloji Günlüğü on March 2, 2008

  796. [...] wordpress.org wird hier etwas zum wichtigen Update geschrieben und was man tun sollte(naja, updaten logischerweise auch). [...]

    Pingback from Uwe » » WordPress 2.1.2 on March 3, 2008

  797. [...] Apa yang harus dilakukan? Jika anda mendownload wp-2.1.1 dalam rentang tanggal 27-februari sampai 2 Maret, segera update wordpress anda ke versi wp-2.1.2. Berita selengkapnya silakan baca di situs wordpress. [...]

    Pingback from destroy! wordpress-2.1.1 Kena Hack « on March 9, 2008

  798. [...] install. You may also remember when WP 2.1.1 got released. A hacker had broken into WordPress and placed a backdoor in the new version of code. This may be unlikely to happen again (hopefully), but it [...]

    Pingback from BlogSecurity » Blog Archive » When to Upgrade your Software on April 11, 2008

  799. [...] download-package was replaced with a version that included some backdoors to implement php code. Official statement / German news (at heise) / Upgrade [...]

    Pingback from tom’s blog » Blog Archive » WordPress-Release 2.1.1 vulnerable on April 11, 2008

  800. [...] Source Related PostsXbox 360 Warranty Boosted to One YearMicrosoft is in the giving mood for the holidays …Was iPhone worth the hype??I had been contemplating writing in this topic for…Blog upgraded to WordPress 2.1Wordpress, the software that powers most of the bl…Popularity: 1% [?] [...]

    Pingback from WP Security Update:2.1.3 and 2.0.10 on April 12, 2008

  801. [...] WordPress 2.1.1 dangerous, Upgrade to 2.1.2. WordPress.org (2 March 2007). Retrieved on [...]

    Pingback from WordPress » Blog Archive » what is WordPress on April 19, 2008

  802. [...] secure, it seems that WordPress has been having more than its fair share of issues. There was the “highly exploitable code” in May 2007. Then there was the December 2007 update to version 2.3.2, “an urgent security [...]

    Pingback from Time to Leave WordPress? | Mind Muse on April 26, 2008

  803. [...] It’s wise not to upgrade to 2.1.1 so hurry. V2.1.1 was hacked by a “cracker”. [...]

    Pingback from Lukewarm » Blog Archive » Upgrade to 2.1.2 on April 26, 2008

  804. [...] WordPress Announced Exploited 2.1.1 [...]

    Pingback from WordPress 2.1.1 Vulnerabilities, Masih banyak Korban | DJAROT STUDIO'S on April 30, 2008

  805. [...] WordPress 2.1.1 Dangerous, Upgrade [...]

    Pingback from WordPress 2.1.1 有安全漏洞 | 大砲開講 on May 4, 2008

  806. [...] After nearly three weeks of downtime, the site is back up. The move from my own little blogging tool to WordPress has been relatively painless… There was a small performance issue with 2.1 (which was rather drastic on my 64 meg VM), but the latest patch to 2.1.2 seems to have addressed this, as well as a security exploit. [...]

    Pingback from gregs » Blog Archive » Back!! on May 12, 2008

  807. [...] menggunakan versi 2.1.1 wordpress, eh tadi pagi saya lihat di news feednya wordpress sudah keluar versi 2.1.2. Berita tersebut mengharuskan setiap pengguna versi 2.1.1 untuk update keversi teranyar tersebut. [...]

    Pingback from Sudah Harus Update Lagi | MicoKelana Daily Share on May 15, 2008

  808. [...] a déjà connu une archive officielle piratée [...]

    Pingback from WordPress Mu pour gérer son réseau de blogs on May 19, 2008

  809. [...] an update to the systems issue we had last month, we have taken dozens of additional precautions with the servers and systems that run WordPress.org [...]

    Pingback from zlotkus.lt » Blog Archive » Security releases: WordPress 2.1.3 and 2.0.10 on May 26, 2008

  810. gran roulette casino…

    The main thing about free music nextel real ringtones interest free payday loan vincere alla roulette online casino online gratis regeln zu poker…

    Trackback from completely instant loan online payday on May 26, 2008

  811. [...] release.  Apparently, there was a security concern about WordPress2.1.1 that I thought was solid, until further investigation. This is nothing against WordPress. I’m the webmaster of my site, and I should know to keep [...]

    Pingback from The Creative Component Re-Design » Blog Archive » is there life after google? on June 6, 2008

  812. [...] tras haber pasado menos de dos meses desde la salida de WordPress 2.1, se vieron obligados a sacar la versión 2.1.2 ya que un cracker introdución código malicioso en el SVN de desarrollo. Por otro lado la rama de WordPress 2.0 seguía adelante con la versión [...]

    Pingback from La historia de WordPress hasta el día de hoy | aNieto2K on July 14, 2008

  813. [...] If you’re running Word Press version 2.1.1, you need to upgrade right away! Word Press has declared the entire version dangerous. [...]

    Pingback from The Big Word Press Upgrade » Daily Twaddle on July 21, 2008

  814. [...] Si è verificato un accesso non autorizzato in uno dei server di WordPress.org e sono stati compromessi i file di installazione di WordPress. Per non incorrere in inutili rischi [...]

    Pingback from rbnet.it » Archivio blog » Aggiornate subito a WordPress 2.1.2! on August 9, 2008

  815. [...] exactly when the code was modified so you could be at risk!If your curious read the announcement here” from the Official WordPress Development [...]

    Pingback from Habari Testbed :: WordPress 2.1.2 on August 13, 2008

  816. [...] lisää syitä vaihtaa mogblotoriin? Lisää aiheesta -> wordpress.org [...]

    Pingback from WP 2.1.1 hakkeroitiin at Kill the Radio on August 22, 2008

  817. [...] If you use WordPress and have upgraded to version 2.1.1 in the last week or so, you really should read this. [...]

    Pingback from Political Penguin » Something for all WordPress users on September 1, 2008

  818. [...] A fellow blogger’s wordpress site was recently hacked. Please take note of how to secure your wordpress blogs. It involves a bit of technical know-how, so some of you might need to ask help from an IT expert. I have a strong suspicion that Tess’ website was hit by the latest security vulnerability. [...]

    Pingback from How To Secure Your WordPress Blog | *Jozzua on September 20, 2008

  819. [...] Backdoored Version (more) [...]

    Pingback from WordPress BlogWatch : Secure FreeBSD | Home on September 20, 2008

  820. [...] Read more at the WordPress site. If you’re running anything older than v2 you might want to consider upgrading too.     Read More    [...]

    Pingback from Paul Henman - find me at henman.ca » Blog Archive » WordPress 2.1.1 dangerous, Upgrade to 2.1.2 on September 28, 2008

  821. [...] tespit edildi. Bu durum üzerine WordPress.org gerekli düzenlemeleri yapıp 2.1.2 sürümünü yayınladı. Eğer son 3-4 gün içinde WordPress.org’dan İngilizce son sürümü indirip kurduysanız [...]

    Pingback from TamBlog.Gen.Tr » WordPress 2.1.2 TR on October 18, 2008

  822. [...] have know vulnerabilities. Right now the checks are limited to WordPress 2.1.1, which has some serious security issues, but if this is a success the service will be expanded to include checks for other software. You [...]

    Pingback from Google notifying webmasters of security vulnerabilities - Security and the Net on October 23, 2008

  823. [...] take the time out to look at it, and yet it may contain an XSS or DOM injection, or it may contain malware if the download is corrupted, or a fake version comes [...]

    Pingback from Decoding wp-admin/js/revisions-js.php easter egg at cat slave diary on November 26, 2008

  824. [...] out of date WordPress installs. Due to the large number of WordPress installs on my server, and a reluctance to run bleeding edge software, I’d been a little remission updating WordPress. While none of my installs were more than a [...]

    Pingback from Hummingbird Mentality : WordPress Hack Attack on January 11, 2009

  825. [...] 官方說法: WordPress 2.1.1 dangerous, Upgrade to 2.1.2 [...]

    Pingback from WordPress 2.1.2 Release « roid in TW on February 3, 2009

  826. [...] has been a security breach and you need to upgrade again immediately. All of the details are at WordPress.org but here’s a quick snippet:Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 [...]

    Pingback from WordPress Security Breach - Clueless Wonder on February 28, 2009

  827. [...] कर रहे हैं। वर्डप्रेस के द्वारा जारी नई खबर के अनुसार वर्डप्रेस का अब तक का [...]

    Pingback from वर्डप्रेस 2.1.1 “खतरनाक” है at इधर उधर की on March 20, 2009

  828. [...] WordPress 2.1.1 exploit – The curious case of hacking a Web application to hack another Web app! [...]

    Pingback from Web application security guidelines and checklist - Jayson Online - Articles & Projects on March 26, 2009

  829. [...] netop er så udbredt. Ikke et ondt ord om wordpress, selvom de har været uheldige til tider med falske opdateringer og den [...]

    Pingback from CMSKonsultent.dk » WordPress hacking er mere udbredt end du tror… on March 27, 2009

  830. [...] Ve sonrasında başlangıç sayfasındaki son haberlere göz atayım dedim. En güncel haber olarak WordPress 2.1.1 dangerous, Upgrade to 2.1.2 karşıma çıktı. Açıkcası daha yeni yayınlanmış, ve haberin üstünden 2 saat geçmişti. [...]

    Pingback from Demo page » Blog arşivi » WordPress 2.1.2 Çıktı on April 21, 2009

  831. [...] lokalisierte deutschsprachige Variante, zu beziehen hier, ist nicht betroffen – es traf die Originalversion des Downloads auf einem wordpress.org-Server. Trotzdem wurde die Version 2.1.1 als gefährlich und [...]

    Pingback from Auch das ist OpenSource — Amys Welt on August 5, 2009

  832. [...] was not surprising to see items such as WordPress 2.1.1 Dangerous, Upgrade beginning to appear early in 2007. Nor was it difficult to believe that Matt Cutts WordPress Blog [...]

    Pingback from WordPress Blog Hacked | BPWrap on August 20, 2009

  833. [...] this hack news from June 2008 or March 2007 But this news .. news .. news .. news [...]

    Pingback from VeryTAS | Reality Is » Hackage, Snackage, Package on September 6, 2009

  834. [...] has been a security breach and you need to upgrade again immediately. All of the details are at WordPress.org but here’s a quick snippet: Long story short: If you downloaded WordPress 2.1.1 within the [...]

    Pingback from Clueless Wonder » Blog Archive » WordPress Security Breach on September 20, 2009

  835. [...] WordPress [...]

    Pingback from WordPress 2.1.1 Hacked, Upgrade Immediately « Geekmass on September 26, 2009

  836. [...] "WordPress 2.1.1 dangerous, Upgrade to 2.1.2". WordPress.org. 2 March [...]

    Pingback from Vulnerabilităţi WodPress | Sit web on October 7, 2009

  837. [...] An unknown intruder has compromised a WordPress server and added a remote control tool to downloadable versions of the widely used blogging software. The breach happened last week and was discovered on Friday, WordPress creator Matt Mullenweg wrote on the WordPress Web site. [...]

    Pingback from ReleaseTest » Intruder adds back door to WordPress blog software! on October 12, 2009

See Also:

For more WordPress news, check out the WordPress Planet.

There’s also a development P2 blog.

To see how active the project is check out our Trac timeline, it often has 20–30 updates per day.

Categories

%d bloggers like this: