WordPress update for the recently discovered security bug (SQL injection) is out just now - WP 1.5.1.2. Go ahead and update your installations now.
Related Entries:
- Important Security fix on WordPress 2.5.1
- All up on WordPress. 2.5 Final Release
- Time for WordPress 2.1.3 and 2.0.10
- WordPress 1.5.1.3 Security Update
- Security Upgrade to WordPress 2.2.2 & 2.0.11
- WordPress and FireFox Upgrades
- Wordpress 2.0 draws near
- The Security Device has Arrived
- Wordpress 1.5.1.3 now available.
- Early Friday Roundup
3 Responses to “WordPress 1.5.1.2 Security Update”
Leave a Reply
Ad Links
Subscribe
Sponsors
 |
|
| Free ringtones for your mobile phone. Get the latest mobile ringtones & wallpapers. Download the most popular ringtones for all phone models. Motorola ringtones available at Adiusa.com. | |
|
Send money to Philippines using iKobo. The recipient receives Visa Debit Card. Online money transfer from iKobo.
Weekly Poll
Loading ...Photo Press
Recent Posts
- Nikon D700 12.1MP FX: Spiffy & Pricey
- Paid Blogging Gigs
- What will happen to Globe Visibility Unlimited?
- Voodoo Envy 133: Thinner than Air?
- Want some YMail or RocketMail accounts?
- Globe Visibility Mobile 3G goes Prepaid
- The Typhoon that busted my DSL Modem
- Google Trends for Websites
- Samsung Instinct released on Sprint
- The Yahoo! Exodus has just began
- Over 26k FF3 downloads from the Philippines
- Benchmarking the Intel Core 2 Duo E8500
- Firefox 3 Download Day goes kaput!
- Technorati Media launches Blog Ad Network
- Sony Ericsson c905 sports 8.1MP Camera
- Optimizing Camera Phone Settings
- Nokia E71 & E66 announced
- HP, Dell and Acer still lead in Laptop Market
- HTC Touch Dual Review
- Guinness World Records 2008 & Internet Record Breakers
An apparent weakness of weakly typed languages. Nonetheless, they fixed the bug in 40 minutes.
Teh Bug was featured on one of astalavista[dot]com’s
Astalavista Top 20 Featured Papers (on bugs and exploits)
A month ago (i think *scratch*), atleast we dont have to
worry that no more (nga ba?) hehe. tnx 4 the reminder!
This is a new bug, actually, found just yesterday morning. The patch was released in less than 40 minutes after it was discovered.