CVE-2024-28387 is a vulnerability identified in Axonaut, a business management software, specifically affecting versions 3.1.23 and earlier. The issue arises from the log.txt component, which improperly stores sensitive information in cleartext, violating secure logging practices (CWE-312). Additionally, the vulnerability relates to CWE-359, indicating that sensitive data exposure occurs through logs that are accessible without adequate protection. Because the vulnerability can be exploited remotely without authentication or user interaction (CVSS vector AV:N/AC:L/PR:N/UI:N), an attacker can directly access the log.txt file to retrieve confidential information. The CVSS score of 7.5 reflects a high severity due to the ease of exploitation and the high impact on confidentiality. Although no known exploits have been reported in the wild, the absence of patches increases the urgency for organizations to implement interim controls. The vulnerability does not affect data integrity or system availability but poses a significant risk of data leakage, which could lead to further attacks or compliance violations. The lack of patch links suggests that vendors have not yet released a fix, emphasizing the need for defensive measures such as access restrictions and monitoring.

The primary impact of CVE-2024-28387 is the unauthorized disclosure of sensitive information stored in the log.txt file of Axonaut software. This breach of confidentiality can lead to exposure of business-critical data, client information, or internal operational details, potentially resulting in reputational damage, regulatory penalties, and facilitation of subsequent attacks such as social engineering or targeted intrusions. Since the vulnerability requires no authentication and can be exploited remotely, the attack surface is broad, increasing the risk for organizations using affected versions. Although integrity and availability are not directly compromised, the leakage of sensitive data alone can have severe consequences for organizations, especially those handling sensitive financial or personal information. The absence of known exploits in the wild currently limits immediate widespread impact, but the vulnerability remains a significant threat until patched.

Organizations should immediately restrict access to the log.txt file by implementing strict file permissions and network access controls to prevent unauthorized remote retrieval. Monitoring and logging access to this file can help detect suspicious activity early. Until a vendor patch is released, consider isolating affected Axonaut instances from untrusted networks or deploying web application firewalls (WAFs) to block unauthorized requests targeting the log.txt resource. Review and sanitize logging configurations to ensure sensitive data is not recorded in plaintext. Engage with the vendor for timely updates and apply patches as soon as they become available. Additionally, conduct regular audits of log file storage and access policies to prevent similar vulnerabilities. Educate staff on the risks of sensitive data exposure and enforce least privilege principles for system access.