De AI ChatBot voor WordPress is kwetsbaar voor Directory Traversal in versies tot en met 4.8.9 en 4.9.2 via de qcld_openai_upload_pagetraining_file functie. Dit stelt abonnees in staat

An attacker exploiting CVE-2023-5241 can leverage the directory traversal vulnerability to append malicious code, specifically "<?php", to existing files on the WordPress server. This is particularly dangerous when targeting critical files like wp-config.php. By injecting this code, an attacker can disrupt the WordPress installation, potentially leading to a complete denial of service. The ability to append code to core configuration files could also allow for further exploitation, although the immediate impact is primarily DoS. The vulnerability's ease of exploitation, combined with the potential for widespread impact, makes it a significant security concern.

Websites utilizing AI ChatBot for WordPress, particularly those with subscriber-level users who have file upload privileges, are at significant risk. Shared hosting environments where users have limited control over file permissions are especially vulnerable. WordPress installations with outdated versions of AI ChatBot are also at high risk.

• wordpress / composer / npm:

grep -r "qcld_openai_upload_pagetraining_file" /var/www/html/wp-content/plugins/

• wordpress / composer / npm:

wp plugin list | grep ai-chatbot

• wordpress / composer / npm:

wp plugin update ai-chatbot

• generic web: Review WordPress access logs for unusual file upload attempts, particularly those involving path traversal sequences (e.g., ../).

1. 2023-10-19Disclosure

   disclosure

2. 2023-10-19Patch

   patch

1. Gereserveerd2023-09-27
2. Gepubliceerd2023-10-19
3. Gewijzigd2025-06-12
4. EPSS bijgewerkt2026-04-02

The primary mitigation for CVE-2023-5241 is to immediately upgrade AI ChatBot for WordPress to version 4.9.3 or later. If upgrading is not immediately feasible, consider implementing a temporary workaround by restricting file upload permissions for subscriber-level users. Review server access logs for any suspicious file modification attempts. While a WAF might offer some protection, it's unlikely to be effective against this type of vulnerability without specific rules tailored to the qcldopenaiuploadpagetrainingfile function. After upgrading, verify the fix by attempting to upload a file with a malicious filename (e.g., ../../../../wp-config.php<?php) and confirming that the upload is rejected.

Actieve installaties

6KPopulair

Plugin-beoordeling

4.7

Vereist WordPress

4.6+

Compatibel tot

7.0

Vereist PHP

5.6+