Which products and versions are affected by CVE-2018-8719?

Affected: Wp Security Audit Log (Wpsecurityauditlog) versions 3.1.1. The full list is in the CVE brief.

Is CVE-2018-8719 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2018-8719 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2018-8719?

Public exploit code is available.

Is there a fix for CVE-2018-8719?

Fixed versions are available, including Wp Security Audit Log 3.1.2.

How urgently should CVE-2018-8719 be patched?

Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Request A Demo

Vulnerability Intelligence

CVE-2018-8719

MediumPublic exploit

Access to wp-content/uploads/wp-security-audit-log/* files is not restricted.

Published Apr 4, 2018 · Updated Nov 21, 2024 · Also known as 12837ce3-eeeb-4034-a90d-fc615056a818

Key Facts

Routine patching

CVE-2018-8719 is a medium-severity vulnerability (CVSS 5.3 v3.1) affecting Wp Security Audit Log (Wpsecurityauditlog).
It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
EPSS estimates a 16% probability of exploitation in the next 30 days.
Fixed versions are available, including Wp Security Audit Log 3.1.2.
Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

CVSS v3.1

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS (30-day exploit likelihood)

16%

Higher than 96.8% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2018-8719 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

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.

Affected Products

2 affected entries in total

Product	Affected versions	Fixed in
Wp Security Audit LogWpsecurityauditlog	3.1.1	3.1.2

Patched Releases

Wp Security Audit Log

3.1.2

Timeline

Publicly disclosed
Apr 4, 2018
Last updated
Nov 21, 2024

Weakness Type

CWE-532 Insertion of Sensitive Information into Log File

References

FAQ

Common Questions.

An issue was discovered in the WP Security Audit Log plugin 3.1.1 for WordPress.
Affected: Wp Security Audit Log (Wpsecurityauditlog) versions 3.1.1. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including Wp Security Audit Log 3.1.2.
Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Is CVE-2018-8719 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.