In versions up to and including 4.9.2 of the Secure Copy Content Protection and Content Locking plugin, exported CSV files containing sensitive user information such as emails, IP addresses, usernames, roles, and location data are stored in a publicly accessible directory. The filenames of these CSV files follow a predictable pattern, making it easy for unauthenticated attackers to locate and access them. This issue arises from an insecure default configuration that fails to adequately protect sensitive data. Attackers can leverage this flaw to gather personal information about users, potentially leading to further attacks such as phishing or identity theft. The lack of access restrictions on the directory storing these files exacerbates the exposure risk, as no authentication is required to download the data. Proper file access controls and secure storage configurations can mitigate such vulnerabilities.

To mitigate this vulnerability, ensure that sensitive data files are stored in a non-public directory with strict access controls. Apply a security-focused configuration to disable direct access to the directory containing exported CSV files. Additionally, utilize permissions and .htaccess rules (if applicable) to restrict unauthorized access to these files.