Staff replied SP Page Builder

Manual Upload SP Page Builder

Asked by Pietro Perlingieri 3 months ago Last activity 2 months ago

Hello, after hacked site, We renewed the license to fix the issue, but in the meantime, the site was compromised! Now the page builder section isn't working, and the pages managed by it cannot be edited via the backend because the application is down. We need to update, but doing so from the backend isn't possible due to the error mentioned in the previous message. I’d like to proceed with the update via FTP; could you tell me which files go into which folders? I’ll handle the database update via phpMyAdmin.

Awaiting your instructions.

6 replies

Ziaul Kabir Staff

3 months ago

Hello,

We sincerely apologize for the inconvenience caused.

This issue has been fixed in SP Page Builder v6.6.2. Once you upgrade to v6.6.2, this specific vulnerability can no longer be exploited.

However, if your site was compromised before upgrading, simply updating the extension will not remove any malicious files or backdoors that may have already been uploaded. If those files remain on the server, attackers may still be able to access your site. Therefore, it is important to perform a complete cleanup before considering the site secure.

Please follow the cleanup guide here: https://www.joomshaper.com/forum/question/45152
You can also use the following security scanner to help identify malicious files and delete them: https://github.com/zkrana/joomla-security-scanner

Please make sure to read the README.md file in the repository for instructions on how to run the tool.
After completing the cleanup and upgrading to v6.6.2, please let us know the outcome or if you need any further assistance.

We'll be happy to help.
Thank you.

Pietro Perlingieri Asked this

3 months ago · edited

Hi,
I’ve cleaned up the site and applied the patch to the assets.php file, but now I need to update the entire SP Page Builder PRO plugin, and the Joomla installer isn't working for this.

Error:
JInstaller: :Install: SQL Error Duplicate column name 'is_single_location' Extension installation aborted. × danger Component installation error

Could you tell me which files to upload manually and to which folders, as well as provide the SQL to update the database?
Thanks in advance!

Ziaul Kabir Staff

3 months ago

Hi,

Thank you for the update.

To investigate the issue properly, could you please share an Akeeba Backup of your website in ZIP format with us? This will allow us to reproduce the problem in a local environment and identify the cause of the installation error more efficiently.

Once the backup is ready, please upload it to a cloud storage service (such as Google Drive or Dropbox) and share the download link here. If the backup is too large, you can also share only the site files and database separately.

We'll review it and get back to you with a solution as soon as possible.

Thank you!

Pietro Perlingieri Asked this

3 months ago

I'm sorry, but it is not possible to proceed with Akeeba Backup due to sensitive data protection.
But the question is easy i mean... Is there no way to update the component without going through the Joomla installation process?

Thank you.

Ziaul Kabir Staff

3 months ago

Yes, you can do that.

Please create a staging site with a fresh installation of Helix Ultimate and install the latest version of SP Page Builder. Then, copy the SP Page Builder folder from this site to the live site and check whether the issue can be fixed or not.

Thank you.

Pietro Perlingieri Asked this

3 months ago

I’ve resolved the issues.
There are two causes:

In script 6.3.0:
ALTER TABLE #__nome_tabella
ADD is_single_location TINYINT(1) NOT NULL DEFAULT 0;

--> It throws an error if the column already exists; please add a check for this. I was upgrading from version 5.3.2.

The table creation script: CREATE TABLE IF NOT EXISTS esi24_sppagebuilder_versions

It throws an error:

1005 - Can't create table db0_digitaesi.esi24_sppagebuilder_versions (errno: 150 "Foreign key constraint is incorrectly formed")

...because the table
esi24_sppagebuilder(id)
is MyISAM rather than InnoDB (due to a previous migration).

I hope this helps.
That bug was a huge problem!! The site was down for two weeks... and I had to find the solution myself.
Thanks, Support.

Ziaul Kabir Staff

2 months ago

Hi Pietro,

Thank you for taking the time to share your findings and the solution you discovered.

We're very sorry to hear about the difficulties you experienced and that your site was down for such a long time. We completely understand how frustrating that must have been, especially after dealing with the security incident.

We sincerely appreciate your understanding and support.