Author Topic: Possible CWP Security Issue – Malicious JavaScript Injection  (Read 448 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Re: Possible CWP Security Issue – Malicious JavaScript Injection
« Reply #15 on: August 27, 2026, 01:03:52 PM »
In response to overseer ... Big Thanks for the advice!..:..

Trying to add to the forum here as well.

The access_log was over 3 gbs in size.
...
Is it safe to delete these two periodically on my own?
My advice:
Code: [Select]
truncate -s0 /usr/local/cwpsrv/logs/access_log
truncate -s0 /usr/local/cwpsrv/logs/error_log
Then look at File Management >  Logrotate Manager and add a rotation job for those files.

Added the following conf file into the log rotation tool

/usr/local/cwpsrv/logs/*_log {
    daily
    missingok
    notifempty
    rotate 14
    compress
    delaycompress
    copytruncate
}

This is tested and working. Use/edit  it at your own risk :) Notice the copytruncate at the end...learned the hard way that was needed, without it the the cwp process seemed to hold the file and continued writing into the copied file, not a good thing., The log rotation cron then did not create the log file. I am guessing that with a service bounce the original log file would be created.

Hope that this helps someone



« Last Edit: August 27, 2026, 01:06:30 PM by audept »

Online
*
Re: Possible CWP Security Issue – Malicious JavaScript Injection
« Reply #16 on: August 27, 2026, 06:47:47 PM »
@murad99

Is there a reason you are still running CentOS 7, a past EOL OS?
That alone is a massive security hole.

The past several weeks they have been Kernel updates almost every other day, at least for AL9 and AL10.

But to close some of the security holes, I would updated your:

Base PHP to at least 8.3.33 and the PHP-FPM for the websites. (I'm glad CWP finally got PHP updated)
Apache is at 2.4.68
Nginx is at 1.30.4

jQuery has several notable past Common Vulnerabilities and Exposures (CVEs) related to Cross-Site Scripting (XSS) and DOM manipulation.
(There are 137 entries just for jQuery)

That's not counting the CVE's for CentOS 7, Apache <2.4.68, Nginx <1.30 and PHP <8.3.33

Our AlmaLinux 9 servers are all OK.
But we try to keep everything updated on the server side, unfortunately that doesn't work with some users. :/


As I mentioned at the beginning of this thread, I observed the same issue on two different CWP servers, and one of those servers was running AlmaLinux 9.

I agree that the older versions on my CentOS 7 server are my responsibility, and I am not trying to argue otherwise. However, I want to emphasize that I also found the same injected jQuery files on an AlmaLinux 9 server.

I am not particularly concerned about my own server in this case; I decided to report the issue publicly because I believe there may be something worth investigating.

I have shared what I found. The interpretation and conclusion are ultimately up to the CWP team and the community.

One more thing I would like to mention: it appears that registering on the forum with a Gmail address is currently not working, as the confirmation email does not arrive. This may give the impression that forum registration is disabled. There may be other users experiencing the same issue who are currently unable to report their findings or ask for help here.

I thought it was worth mentioning this as well.

Offline
*****
Re: Possible CWP Security Issue – Malicious JavaScript Injection
« Reply #17 on: August 27, 2026, 08:29:28 PM »
I can't keep up with CVE's for WordPress, and gave up.

But as long as you keep Apache updated, and have Mod Security installed, running the latest OWASP rules, you should be OK for the most part.

Unless again, WordPress or a WordPress plugin allows something in.

CWP hasn't had a CVE since last year (CVE-2025-67888), which was fixed with 0.9.8.1209
CVE-2025-48703 was fixed in 0.9.8.1205

There are 16 CVE's that just came out today (2026-08-27) for OpenSSL:
CVE-2026-81683
CVE-2026-81700
CVE-2026-81701
CVE-2026-81702
CVE-2026-81707
CVE-2026-81704
CVE-2026-81705
CVE-2026-81706
CVE-2026-81714
CVE-2026-81715
CVE-2026-81716
CVE-2026-81717
CVE-2026-81718
CVE-2026-81719
CVE-2026-81720
CVE-2026-81721

And 3 for Plesk:
CVE-2026-65642 (Allows you to gain access to other users databases)
CVE-2026-65646
CVE-2026-65647 (Allows code to be run as root)
« Last Edit: August 27, 2026, 08:31:39 PM by Starburst »

Offline
*****
Re: Possible CWP Security Issue – Malicious JavaScript Injection
« Reply #18 on: August 27, 2026, 08:34:07 PM »
Hmm what was going down in November? Been many challenges in 2026 I can't remember.

Search says this was current then CVE-2025-48703

These where the 2 last CVE's for CWP in 2025:

CVE-2025-67888 was fixed with 0.9.8.1209
CVE-2025-48703 was fixed in 0.9.8.1205

Online
*
Re: Possible CWP Security Issue – Malicious JavaScript Injection
« Reply #19 on: August 27, 2026, 11:49:07 PM »
I can't keep up with CVE's for WordPress, and gave up.

But as long as you keep Apache updated, and have Mod Security installed, running the latest OWASP rules, you should be OK for the most part.

Unless again, WordPress or a WordPress plugin allows something in.

CWP hasn't had a CVE since last year (CVE-2025-67888), which was fixed with 0.9.8.1209
CVE-2025-48703 was fixed in 0.9.8.1205

There are 16 CVE's that just came out today (2026-08-27) for OpenSSL:
CVE-2026-81683
CVE-2026-81700
CVE-2026-81701
CVE-2026-81702
CVE-2026-81707
CVE-2026-81704
CVE-2026-81705
CVE-2026-81706
CVE-2026-81714
CVE-2026-81715
CVE-2026-81716
CVE-2026-81717
CVE-2026-81718
CVE-2026-81719
CVE-2026-81720
CVE-2026-81721

And 3 for Plesk:
CVE-2026-65642 (Allows you to gain access to other users databases)
CVE-2026-65646
CVE-2026-65647 (Allows code to be run as root)

Thank you, Starburst, for taking the time to look into this and for sharing your insights.

If you ever need help with anything here, I’m sure many people on this forum would be more than happy to help. Just start a thread and see what happens. :)