Potential Security Vulnerability In SP Page Builder 6.6.2 - Asset.uploadCustomIcon Endpoint - Question | JoomShaper

Celebrate JoomShaper's Sweet 16 with Flat 35% OFF!

Potential Security Vulnerability In SP Page Builder 6.6.2 - Asset.uploadCustomIcon Endpoint

Balogh Viktor

Balogh Viktor

SP Page Builder 19 hours ago

We noticed there is already another thread discussing suspicious activity around the uploadCustomIcon functionality, but we decided to open a separate topic because we have now collected concrete forensic evidence from a production environment.

We are running:

Joomla 6.1.1 (latest version) SP Page Builder Pro 6.6.2 Official licensed version downloaded directly from JoomShaper No nulled extensions or modified packages

Over the last 24 hours we observed a large number of automated attacks targeting the following endpoint:

index.php?option=com_sppagebuilder&task=asset.uploadCustomIcon

Our hosting provider's malware protection system logged multiple upload attempts from different IP addresses worldwide. The uploaded payloads contained PHP webshells hidden inside ZIP archives.

The malware scanner reports clearly show the requests being processed through:

option=com_sppagebuilder&task=asset.uploadCustomIcon

and the extracted files appearing under:

/media/com_sppagebuilder/assets/iconfont/<random>/fonts/

During the investigation we recovered an actual webshell from that directory:

/media/com_sppagebuilder/assets/iconfont/icoclfsko/fonts/fmbhvzr.PHP

Based on the logs, the attack pattern appears to be:

Direct frontend request to asset.uploadCustomIcon Upload of a ZIP archive Archive extraction into the iconfont directory Creation of executable PHP files Remote command execution

At the moment we have mitigated the issue by:

Blocking task=asset.uploadCustomIcon via .htaccess Disabling PHP execution inside /media/com_sppagebuilder/ Removing all discovered shells

Can the development team please clarify:

Is this a known issue? Should this endpoint require administrator authentication? Has a security fix already been released? Is there any official mitigation available?

Any feedback would be greatly appreciated, as this is currently affecting multiple production websites.

Thank you.

0
2 Answers
MiBa
MiBa
Accepted Answer
19 hours ago #226622

Compromised site after cleaning and update to SPPB 6.6.2 show HTTP status 403.

from Apache log:

58748: somesite.xyz:80 88.167.123.203 - - [23/Jun/2026:13:59:54 +0200] "POST /index.php?option=com_sppagebuilder&task=asset.uploadCustomIcon HTTP/1.1" 301 621

58749: somesite.xyz:443 88.167.123.203 - - [23/Jun/2026:13:59:54 +0200] "GET /index.php?option=com_sppagebuilder&task=asset.uploadCustomIcon HTTP/1.1" 403 6480

Database should be checked too, table menu and sppagebuilder_assets. These hints are in the inital topic of this issue.

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 18 hours ago #226624

@Victor , we have separate topic >> https://www.joomshaper.com/forum/question/45152 with all answers, security tips/codes and stories.


Malware could be hidden a days before you updated SPPB and noticed any signs. We informed about that too. And yes, the last update 6.6.2 fixed that problem, but no extension update can remove hidden malware files; as a webmaster, you should know that. Clean, cure and secure your websites wise! I wish you luck.


Sorry, but duplicated topics making only extra mess!

0