audihertz

Posting an update…

After pounding my head over this, I’ve found evidence of the site getting hacked.

Inside an upload directory from last month (which was the last time the user had uploaded anything to WordPress while using a version prior to 2.8.4), I found an interesting PHP file. It was an obvious, faked Facebook login page that warned a user that a ping.fm link they clicked on was taking them away from Facebook. Obviously this was a mining scheme to harvest people’s Facebook logins.

So now what I’m thinking is after doing an upgrade in the madness the stemmed from the announcements from Automattic, it would appear that the site was the victim of a hack in the SQL level as well. I can’t say if it’s related to the pre-2.8.4 vulnerability because I haven’t found evidence to say either way.

That being said, the author of the site had only been using WordPress for about a year this November, and the size of her SQL table is just about 180MB in size. There are no plugins they have been using in that time to make it that bloated.

I’m going to give it more insight tomorrow. Hopefully my progress might get someone some ideas on where I should look next.

John

Sadly, neither of those worked.

Any ideas on what I might try next?

Here’s the htaccess:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

According to the SQL database, this is what the current permalink structure is set to:

/%year%/%monthnum%/%postname%/

Hope that helps.

– John

Further info.. it seems it might be DNS related. I’ve added an entry to /etc/hosts on the server with the server’s hostname and the IP address, and the 20 second wait goes away.

Just wanted to add that I used this on an Apache server and it seemed to really help out. The pages loaded slow, but it’s not on the fastest connection. This WP install is on a server that I setup myself, and it also runs a couple of Drupal installs as well. Seemed to do the trick for now.

Thanks! I might have to check that out.

Additionally, I sent a note to the security folks at WordPress. If anything, it’s just a heads up. My thinking is that this is a problem that was solved with 2.0.4. The fact that I hadn’t upgraded until after the hack might be the answer.

Yes. I realize this might cause another conflict, but don’t know how.

Disregard.

I found a plugin that does what I was looking for. ??

“Post Per Page”
https://girasoli.org/?p=26