CVE-2023-2252 is a vulnerability identified in the Directorist WordPress plugin versions prior to 7.5.4. The issue is classified as CWE-22, which corresponds to an improper limitation of a pathname to a restricted directory, commonly known as a path traversal vulnerability. Specifically, this vulnerability arises because the plugin does not properly validate the 'file' parameter during the import of CSV files. This lack of validation can lead to Local File Inclusion (LFI), where an attacker could potentially manipulate the file path to access files outside the intended directory. However, the vulnerability requires high privileges (PR:H) to exploit, meaning an attacker must have authenticated access with elevated permissions on the WordPress site. The CVSS v3.1 base score is 2.7, indicating a low severity level, with the vector indicating network attack vector (AV:N), low attack complexity (AC:L), no user interaction (UI:N), and no impact on integrity or availability, only a limited confidentiality impact (C:L). No known exploits are currently reported in the wild, and no patches are linked in the provided data, though the vulnerability is fixed in version 7.5.4 and later. The vulnerability could allow an authenticated user to read sensitive files on the server, potentially exposing configuration files or other sensitive data stored on the web server hosting the WordPress site.

For European organizations using the Directorist plugin on their WordPress sites, the impact of this vulnerability is relatively limited due to the requirement for high-level authentication and the low severity score. However, if an attacker gains administrative or equivalent access, they could exploit this vulnerability to read sensitive files on the server, potentially exposing credentials, configuration files, or other sensitive data. This could lead to further attacks such as privilege escalation or lateral movement within the network. Organizations in sectors with strict data protection regulations, such as finance, healthcare, or government, could face compliance risks if sensitive data is exposed. Additionally, the reputational damage from a breach involving sensitive data exposure could be significant. Since the vulnerability does not allow remote unauthenticated exploitation or direct code execution, the immediate risk is lower compared to more severe vulnerabilities, but it still represents a potential foothold for attackers with some level of access.

European organizations should ensure that all WordPress plugins, including Directorist, are updated to the latest version (7.5.4 or later) where this vulnerability is patched. Since no patch links were provided, organizations should verify updates directly from the official plugin repository or vendor. Access controls should be strictly enforced to limit administrative privileges only to trusted users, reducing the risk of exploitation by malicious insiders or compromised accounts. Implementing Web Application Firewalls (WAFs) with rules to detect and block path traversal attempts can provide an additional layer of defense. Regular security audits and monitoring of file access logs can help detect suspicious activity related to file inclusion attempts. Finally, organizations should consider isolating WordPress environments and sensitive files to minimize the impact of any potential LFI vulnerabilities.