hicklingadmin

This is the link that Wordfence have provided: https://www.wordfence.com/threat-intel/vulnerabilities/id/2931fda2-edc8-44ea-9fff-ae9d94aa01bf?source=plugin

An update; hopefully, you can help?

We have updated the plugin and we’re running the new version. Unfortunately, the following day, Wordfence sent through a new security alert – the same as before.

Is there a further update solution to come or are you still waiting for a response from Wordfence?

Thank you!

Thank you – we’ll keep plugging on (excuse the pun …).

Thank you for your message; you are right, we are amateurs and we are just looking for some support. I have tried to explain the situation in my original post – as it happens, we are not the only ones experiencing this problem. All the evidence so far points to the 6.3.1 update as the gateway that the hack has come through.

Either way, there is the issue of instability which many users have experienced with the last 2 updates which have meant the update has to be reloaded to recover lost content/function.

We’re not running any out-of-date plugins, we’re not in denial and we’re not stupid with passwords – we’ve had a problem and we’re just looking for some help, please.

We are going through all the processes (because we don’t know for sure what the origin of the problem is) but, if there is an issue with the 6.3.1 update then surely it is better that we’re talking about it and trying to find a fix?

• This reply was modified 1 year, 6 months ago by hicklingadmin.
• This reply was modified 1 year, 6 months ago by hicklingadmin.
• This reply was modified 1 year, 6 months ago by hicklingadmin.

Thank you for your help and advice, George that’s really helpful.

Thankfully, we’re working on the suggestions that you have made already and this is partly why I’ve raised the topic here.

We know that reloading WP 6.3.1 won’t fix the problem but we are in a position where running an old version is unwise and running this new version isn’t secure. Is WP aware of this problem and is there a fix on its way, please?

Update: My website support has reviewed the site and we seem to be all clear now. FooGallery automatically updated overnight 6th/7th September and it looks as if the update addressed whatever the issue was. We deleted the rogue admin that had been created during the breach and there is nothing problematic on the website now, thank goodness.

FooGallery has been reactivated and fingers crossed we’re all OK. Thank you for your help!!

Update: My website support is going to have a proper look at it in the morning. Weirdly, I’ve had two alerts from Wordfence but the Wordfence dashboard is saying ‘no notifications’ and I’ve just run a scan which is coming up clear.

We definitely had a new admin appear on our website dashboard – now deleted. I’ve deactivated FooGallery as a precaution.

No idea what’s happening, I’m afraid.

Thank you so much for getting back to me quickly; this is the system info & then the text at the bottom of the wordfence alert:

• Version: 2.3.3
• Author: FooPlugins
• Last Updated: 21 hours ago
• Requires WordPress: 5.2 or higher
• Compatible up to: 6.3.1
• Active Installations: 100,000+

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.3.1
Active theme: Twenty Twelve (version 4.0)
Current plugin: FooGallery (version 2.3.3)
PHP version 8.1.17

Error Details
=============
An error of type E_ERROR was caused in line 248 of the file /var/www/html/sites/hicklingnottslocalhistory.com/www/wp-content/plugins/foogallery/includes/admin/class-gallery-metaboxes.php. Error message: Maximum execution time of 30 seconds exceeded

Many thanks – the plugin is working again, now.

No idea what the issue was but the gremlin seems to have gone.

Hi, Ben!

Many thanks – the update seems to be working well; no more white dot or updating across the whole site. Reusable blocks are taking a long time to load on editing pages but they seem to be working well.

Thank you!

Jane.

Hi, Ben!

Yes, a bit of an update from me, too – I am having the same problem as Dozent.IS, above; when updating a page which includes a reusable block the system tries to update the whole site (the white dot signal) rather than just the page I’ve been working on. I have had a couple of (occasional) repeats of the original problem where the page freezes when updating after adding a reusable block – perhaps this is because the update is having to work too hard updating across the whole site?

Thank you for your continued help with this!

Hi, Ben!

Many thanks for your help with this – it was a bit clunky to begin with (when I went back to the page I had been editing when the problem emerged) but all working again now. The reusable blocks are still running quite slowly but they are working!

It seems to have sorted out an old problem, too – when I used to delete a reusable block on one page, it deleted from the whole site; so I have been deleting them in the code view instead which didn’t have the same effect. This doesn’t seem to be necessary anymore.

Thank you,

Jane.

Dear Karolina,
You may already have tried this but just in case.
I have found a way around the problem although it really isn’t ideal – it might help in the meantime?
If you go into code editor and remove the code for the reusable block, return to visual editor and then update – then it removes the reusable block from that one page but it stays elsewhere on the website.

Hi! I am now running 5.7.2 and this is still happening – has anyone found a way round it? I am desperate!!! Really hoping that someone can help!

Hi!
I am having the same problem as Karolina; I can’t remove a reusable block from one page without it disappearing from all the pages that it has been used on – I am tearing my hair out! Is there a way of reverting to the old system?