KR. Laboratories

I dont use CF APO.

We can close this discussion. I deleted LiteSpeed Cache WordPress plugin and fix problem.

We have already discussed my settings in previous threads. I can only say that there were no non-standard settings in the plugin. And if there were, I changed them on the advice of qtwrk. And after that, the same thing happened again. One day I went to the site and saw a broken layout. I went to the Chrome Developer console and saw MIME-type errors (this was also described in detail in previous threads). I cleared the LS cache, cleared the CF cache, and then everything returned to normal. But this is not solution.

At first, I thought the problem was with Server Cron, the scheduler was not running, or there was no access to it. But everything is fine here. Then, I checked the cache configuration on the server itself – everything is fine there too. Then I checked Cloudflare, whitelisted access to all the necessary IP addresses. Then everything seemed to suddenly go quiet. And then it happened again.

It’s as if someone who knows about this “hole” is periodically accessing the site and exploiting it. I just assumed that it could be a cache attack. If I had been sure, I would have written a CVE report a long time ago. But this is an assumption. Considering that your plugin already had serious vulnerabilities. There may be a risk of cache manipulation. Also, before that, I noticed a surge in website traffic. Perhaps someone caught up with traffic and overflowed the cache.

The plugin LiteSpeed Cache contains a lot of functionality that hackers can try to exploit. For example, in 2024, at least 10 vulnerabilities of varying degrees were discovered in LS Cache: https://wpscan.com/plugin/litespeed-cache/. And no one knew about it, users only observed various anomalies with the cache. Therefore, I do not dismiss the security problem of your plugin. And I don’t understand how your team of experienced professionals could have allowed such a huge number of vulnerabilities. So where is the guarantee that there is no other hole, no Zero Day?

Unfortunately, I don’t have time to test it now. It’s easier to just remove the WordPress plugin and develop your own solution. No plugin – no problem.

Yes, I wrote an article, and the text simply mentioned /etc/shadow.

As for the image path, it did not affect the triggering.

Analysing the fields, I found only a placeholder that relates to the wordpress functionality:

placeholder="http://…’

Also:

/js/../../images/admin/blockquote-info-ico.png')">

Could this be the reason?

• This reply was modified 1 year, 4 months ago by KR. Laboratories.
• This reply was modified 1 year, 4 months ago by KR. Laboratories.

I perfectly knows what is Directory Traversal attack and review code, but dont find nothing “../”. I think this firewall reaction is caused by Cloudflare proxy. I can’t find any other explanation yet. And frankly, it makes me very nervous because I can’t publish the post properly. And it makes no sense to disable the Traversal module completely, because it creates security risks.

And in my opinion, its not very correct that the blocking is performed on the side of https://safe-load.gotmls.net, and not on the side of my host.

• This reply was modified 1 year, 5 months ago by KR. Laboratories.

Hello,

I recently encountered an issue with the <meta name="viewport"> tag while using the WP Responsive Menu plugin. By default, the plugin modifies the viewport to disable user scaling on mobile devices. After some investigation, I found the option Enable/Disable Scale in the plugin settings, which allowed me to control the scaling behavior.

However, I believe it would be a great enhancement if the plugin provided an option for users to fully customize or override the viewport tag, allowing more flexibility without the plugin intervening.

Would it be possible to add such a feature in a future update, where users can either set their own viewport values or choose to prevent the plugin from modifying the tag altogether?

Best regards

I use FREE VERSION.

No. You are not telling the truth. Your plugin removes Cyrillic names if they contain a space and simply leaves a “-” instead. I understand that this is for security reasons. But then this is a bug in the functionality. Once again, the users who send files through the form are complete strangers to me, and none of them will rename files specifically for me. And your plugin takes these names and deletes them, after which all the files on my server in the folder are named: -.docx. This is a problem. And it needs to be silently fixed. It’s not difficult.

Good luck