Steve

Hi @ninjateamwp

That doesn’t work. As soon as you save it the link is changed back to target=”_blank” – every time.

Perfect, installed and fully functioning.
Thank you

Hey @johnbillion,
Any news on when 1.17 might drop?
Thanks
Steve

Thank you. I’ll keep an eye out for the update.

Thanks @lbell

All updated at this end, WordFence already pleased with the results ??

Thanks. I had assumed it would take some level of site access to exploit but have these warnings coming from all over so thought best to raise it.

A new ModSecurity rule set for Comodo (free) has rolled out within Plesk this morning which seems to have resolved the issue across all my affected sites.

A new ModSecurity rule set for Comodo (free) has rolled out within Plesk this morning which seems to have resolved the issue across all my affected sites.

A new ModSecurity rule set for Comodo (free) has rolled out within Plesk this morning which seems to have resolved the issue across all my affected sites.

All my broken sites are on Plesk using ModSecurity.

WooCommerce versions 8.5.0 and 8.5.1 BOTH trigger ModSecurity to block access with error 403 forbidden.

I’ve resolved this by adding an exception for (switching off) security rule ID 218500. (This rule is: SQLmap attack detected)

This can be done at either server level in Tools & Settings or on a site by site basis under the Web Application Firewall link.

Hope that helps.

All my broken sites are on Plesk using ModSecurity.

WooCommerce versions 8.5.0 and 8.5.1 BOTH trigger ModSecurity to block access with error 403 forbidden.

I’ve resolved this by adding an exception for (switching off) security rule ID 218500. (This rule is: SQLmap attack detected)

This can be done at either server level in Tools & Settings or on a site by site basis under the Web Application Firewall link.

Hope that helps.

• This reply was modified 10 months, 1 week ago by Steve.

Looks to have been resolved ??

Probably suspended for a policy violation looking at one of the ‘tweaks’ in today’s update (1.23.15)

• TWEAK: As required by the www.remarpro.com plugin team, all UpdraftPlus news is forbidden to be displayed in the “WordPress News” section of the dashboard for users of the free plugin even if consent is first given.

@davidanderson

1.23.6 appears to work as expected.

Thank you

Hi @davidanderson

Glad to hear it seems to be a one time event on each site.

Although I must mention my updates have been across at least 6 hosting providers with dedicated, VPN and shared hosting, ALL of which have resulted in same error email.

Every site is doing the same thing:
> Apply update or following auto-update
> Visit the Updraft Backup/Restore page
> Error email arrives