Forum Replies Created

Viewing 4 replies - 16 through 19 (of 19 total)
  • Yes, that’s good advice for most people, even if I wasn’t able to apply it personally (I didn’t have a “known good” backup of the current version, and I’m running Windows).

    @gennady Kovshenin; Thanks for the response, but are there any common telltale signs (e.g.) in logs, etc. in the majority of attacks?

    @tomas Mackevicius at al.

    Note regarding this line;

    select * from wp_options where option_name = ‘mfbfw’;

    Remember to check wp_1_options, wp_2_options, wp_3_options etc. instead if you’re running more than one site on an installation.

    Nothing suspicious appeared on my site(s) when I did this check, but is there a definitive test to confirm whether or not the system has been infected (assuming those using it as an infection vector didn’t clean those up behind them once they’d used it to get in)?

    What is the potential damage that could be caused by this issue? Mention of malicious users in the WP system suggests that it goes beyond cross-site scripting?

    Thread Starter Raspberryade

    (@raspberryade)

    Thanks for your answer. I’ve tried that plugin and it seems to work.

    Bit unfortunate that it won’t work with the existing blog in the /blog subfolder, as that one can’t be moved (our main commerce site lives in the root folder of our primary domain- the reason the blog was put in a subfolder in the first place- and as it’s over two years old, it’ll have been indexed by search engines in that position now).

    Not sure if the added installation and maintenance complexities would outweigh the difficulty of having two or three separate installations instead, but at least I know it works now. Thanks!

    – Raspberryade

Viewing 4 replies - 16 through 19 (of 19 total)