How severe is CVE-2019-6715?

No CVSS score has been assigned to CVE-2019-6715 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2019-6715?

Affected package information for CVE-2019-6715 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-6715?

No fixed release is recorded for CVE-2019-6715 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2019-6715 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2019-6715 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-6715 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2019-6715, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-6715?

CVE-2019-6715 has an EPSS (Exploit Prediction Scoring System) score of 19.4%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is there exploit tooling available for CVE-2019-6715?

A Nuclei detection template exists for CVE-2019-6715, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-6715 published, and has it been updated?

CVE-2019-6715 was published on April 1, 2019 and was last updated on August 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2019-6715

CVE-2019-6715 is a security vulnerability. 4 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via the SubscribeURL field in SubscriptionConfirmation JSON data.

Published

Apr 1, 2019

Updated

Aug 4, 2024

Affected

1 product

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

19.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via the SubscribeURL field in SubscriptionConfirmation JSON data.

Affected Products

1 product · 1 configurations

Application

w3 total cacheboldgrid

< 0.9.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allo…

vinhjaxt.github.ioNVDDec 2020

pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allo…

packetstormsecurity.comNVDDec 2020

pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allo…

github.comGithubNov 2019

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2019-6715 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2019-6715

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-6715 -u https://target

Template: W3 Total Cache 0.9.2.6-0.9.3 - Unauthenticated File Read / Directory Traversal
Severity: high
Impact: An unauthenticated attacker can read sensitive files or traverse directories on the target system, potentially leading to unauthorized access or information disclosure.
Remediation: Update to the latest version of W3 Total Cache plugin (0.9.3 or higher) to mitigate the vulnerability.

Template by ProjectDiscovery nuclei-templates (randomrobbie), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

pub/sns.php in the W3 Total Cache plugin before 0.9.4 for WordPress allows remote attackers to read arbitrary files via the SubscribeURL field in SubscriptionConfirmation JSON data.

O3 Security · Impact-Aware SCA

Is CVE-2019-6715 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2019-6715

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2019-6715

Frequently Asked Questions

Is CVE-2019-6715 in your dependencies?