Have anyone observe this problem?
“WordPress PHP Code Injection Vulnerability”
Yes, it’s been brought to the attn of the devs, and mentioned on the forums 2x today already.
Dare I reply lest this thread is removed also.
This vulnerability will not affect your blog unless the following three criteria are met:
- You have enabled the caching of db info to disk which is disabled by default in 2.0.2
- You have a simple /null database password. This is needed to make the filename of the cache file guessable and the exploit easy to achieve
- You have user registration enabled
Basically for a default 2.0.2 install you are completely safe if you don’t have the cache enabled or user registration is disabled and you are still pretty safe with them enabled unless your db password is easy to guess.
“Dare I reply lest this thread is removed also.”
‘Security’ threads are not usually removed but some people do get overexcited and we’ll start having the “OMG!!11111!!!!! My BloG wiLL bE HacKed!!!!” gang descending in droves, slagging the program off, saying WP takes nothing seriously etc etc etc. That does nothing except give a platform to people who know little but can scare more, and worry those who have no need. It gets really tedious.
The decision to close the thread / respond was taken on the forum list – no coders had any input before that.
Hasty? Possibly, but from experience it turns into firefighting and those threads never ever have a “WP is doing something? Cool, we are all reassured”. If that happened, great. But it doesn’t.
Like Westi has said, this takes a set of circumstances rather than a simple action.
I’ll add that people should take note of (2) above:
“You have a simple /null database password.”
Regardless of ANY exploit the weakest link in your wp install is your password. Make it better.
1. You have enabled the caching of db info to disk which is disabled by default in 2.0.2
Actually, I believe that is enabled by default. At least, my site has the cache, and I never explicitly turned it on.
2. You have a simple /null database password. This is needed to make the filename of the cache file guessable and the exploit easy to achieve
3. You have user registration enabled
If your wp-content is writable, then cache is ON by default in 2.0.2
If your wp-content is NOT writable, then cache is not written but you see no error.
It is therefore ON.
as I wrote here:
Either way, the right people know.
I don’t usually worry too much about “security issues”, because I’m quite sure the “top notches” know of it and things will be dealt with accordingly. =)
I just noticed earlier about 2.0.3 Beta being ready for download and ready for “testing” on the list..so I’m grabbing a copy of that. I’m not sure if those “security issues” were handled in that or not, but I’m just downloading it anyways lol!
EDITED* I meant, I noticed that the “version” was changed to 2.0.3-beta, so I figured I’d grab it.
$wp_version = '2.0.3-beta';
$wp_db_version = 3796;
v2.0.3 is now released with the fix for this included.
- The topic ‘(security issue) WordPress PHP Code Injection Vulnerability’ is closed to new replies.