WP Security Audit Log Plugin 3.1.1 on WordPress wp-security-audit-log log file

Summaryinfo

A vulnerability identified as problematic has been detected in WP Security Audit Log Plugin 3.1.1 on WordPress. This impacts an unknown function of the file wp-content/uploads/wp-security-audit-log/. The manipulation leads to log file. This vulnerability is uniquely identified as CVE-2018-8719. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in WP Security Audit Log Plugin 3.1.1 on WordPress (WordPress Plugin) and classified as problematic. This issue affects some unknown functionality of the file wp-content/uploads/wp-security-audit-log/. The manipulation with an unknown input leads to a log file vulnerability. Using CWE to declare the problem leads to CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. Impacted is confidentiality. The summary by CVE is:

An issue was discovered in the WP Security Audit Log plugin 3.1.1 for WordPress. Access to wp-content/uploads/wp-security-audit-log/* files is not restricted. For example, these files are indexed by Google and allows for attackers to possibly find sensitive information.

The bug was discovered 03/30/2018. The weakness was disclosed 04/04/2018 as EDB-ID 44371 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2018-8719 since 03/14/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.

After immediately, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (44371). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• WP Security Audit Log Plugin

Version

• 3.1.1

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion