• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Vulnerabilities of WordPress

mark_hosting

New Pleskian
Server operating system version
CentOS Linux 7.9.2009
Plesk version and microupdate number
18.0.52 Update #3
When we want to do this I get the following error Internal server error: Specified column "cvssScore" is not in the row
 

Attachments

  • interne server.PNG
    interne server.PNG
    48.6 KB · Views: 14
You can try to run
# plesk repair db -y
to make sure that no database inconsistencies cause this.

If that does not help, for "cvssScore" we don't yet have any specific knowledge on file. I think it is probably caused by a theme or plugin that is not following Wordpress standards. Please open a ticket with Plesk support staff in that case so that the issue can be checked and fixed on your server.
 
In that case it is probably an incompatible theme or plugin that is causing the error. You can easily test this: Simply install another, empty Wordpress instance through Plesk in a fresh subdomain, then check the vulnerabilities there.
 
In that case it is probably an incompatible theme or plugin that is causing the error. You can easily test this: Simply install another, empty Wordpress instance through Plesk in a fresh subdomain, then check the vulnerabilities there.

ya, it's plugin issue in the them because this them required this plugin to work, i bought it premium, i know its not an issue in plesk.
 
Back
Top