I want to bring to your attention a critical security issue with the plugin. It was identified that the plugin is vulnerable to SQL Injection. This poses a significant security risk to the website.
Could you please confirm if a patch or an update is in development to resolve this issue?
We would greatly appreciate your prompt assistance in this matter.
Thank you
]]>what do i do to solve it?
]]>I recently found the following critical issue on my website (pyseek.com), detected by WordPress site health:
“
Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.
Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:
cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status, x-litespeed-cache, x-lsadc-cache, x-qc-cache.
Median server response time was 1,243 milliseconds. It should be less than the recommended 600 milliseconds threshold.
There was 1 client caching response header detected: x-litespeed-cache
“
I’m unable to understand the issue and the solution. Can anyone help me to fix the issue?
Thanks in advance!
Sincerely,
Subhankar Rakshit
I recently found the following critical issue on my website (pyseek.com), detected by WordPress site health:
“
Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.
Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:
cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status, x-litespeed-cache, x-lsadc-cache, x-qc-cache.
Median server response time was 1,243 milliseconds. It should be less than the recommended 600 milliseconds threshold.
There was 1 client caching response header detected: x-litespeed-cache
“
I’m unable to understand the issue and the solution. Can anyone help me to fix the issue?
Thanks in advance!
Sincerely,
Subhankar Rakshit
Hi there -
For the past few days, I've been receiving emails from WP informing me of a critical error. Originally, the error was to do with the Social Stickers plugin (now deleted). Now a new error has been caught by WP - 'with your theme, Headway Base'.
I can't access my website, wp-admin page or recovery page - but I can get to the cPanel. But what to do from there?!
Error Details
=============
An error of type E_ERROR was caused in line 29 of the file /(redacted info)/wp-content/themes/headway/library/api/api-admin-meta-box.php.
Error message: Uncaught Error: Call to undefined function create_function() in /(redacted info)/wp-content/themes/headway/library/api/api-admin-meta-box.php:29
WordPress version 6.5
Active theme: Headway Base (version 3.8.8)
Current plugin: ?(version )
PHP version 8.2.17
I'm reasonably competent at following instructions and would be super grateful if anyone could help me fix this issue. MTIA!
]]>A critical issue was found on a WF scan:
Details: https://example.com/.user.ini is publicly accessible and may expose source code or sensitive information about your site. Files such as this one are commonly checked for by scanners and should be made inaccessible. Alternately, some can be removed if you are certain your site does not need them. Sites using the nginx web server may need manual configuration changes to protect such files. Learn moreThe contents of the file are:
; Wordfence WAF
auto_prepend_file = '/opt/bitnami/wordpress/wordfence-waf.php'
; END Wordfence WAFShould this file be deleted?
The file permission is 664
]]>WP STAGING Shutdown Function][E_COMPILE_ERROR][2023-10-16 21:17:40] require(): Failed opening required ‘/var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/edit-form-advanced.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) – File: /var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/post-new.php Line: 75 | Is it Fatal Error? Yes | Is it Thrown by WP STAGING? No
[WP STAGING Shutdown Function][E_COMPILE_ERROR][2023-10-16 21:17:48] require(): Failed opening required ‘/var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/edit-form-advanced.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) – File: /var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/post-new.php Line: 75 | Is it Fatal Error? Yes | Is it Thrown by WP STAGING? No
[WP STAGING Shutdown Function][E_COMPILE_ERROR][2023-10-16 21:20:30] require(): Failed opening required ‘/var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/edit-form-advanced.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) – File: /var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/post-new.php Line: 75 | Is it Fatal Error? Yes | Is it Thrown by WP STAGING? No
[WP STAGING Shutdown Function][E_COMPILE_ERROR][2023-10-16 22:09:12] require(): Failed opening required ‘/var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/edit-form-advanced.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) – File: /var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/post-new.php Line: 75 | Is it Fatal Error? Yes | Is it Thrown by WP STAGING? No
[WP STAGING Shutdown Function][E_COMPILE_ERROR][2023-10-16 22:10:41] require(): Failed opening required ‘/var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/edit-form-advanced.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) – File: /var/www/vhtdocs/userweb65598/html/jbh-2023/wp-admin/post-new.php Line: 75 | Is it Fatal Error? Yes | Is it Thrown by WP STAGING? No
PHP Fatal error: Uncaught Error: Class 'Smush\Core\Backups\Backups_Backward_Compatibility' not found in /path/to/public_html/wp-content/plugins/wp-smushit/core/class-modules.php:154
It looks like the file /var/www/annacenter/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 13 is declaring the use of namespaced class ‘Backups_Backward_Compatibility’ however the class is not defined anywhere in the plugin. I think same is the case with line 14 usage declaration (Backups_Controller).
]]>