WordPress WP Cafe Pro plugin < 3.0.15 - Sensitive Data Exposure vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps WPCafe/WP Cafe Pro (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for WPCafe/WP Cafe Pro.
2. 2Review the reported fix. Update WPCafe/WP Cafe Pro to 3.0.15 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 24, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 24, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 24, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress WP Cafe Pro plugin < 3.0.15 - Local File Inclusion vulnerabilitySame wpcafe/wp cafe pro package
• HCL Hive is affected by use of a cryptographic primitive with a risky implementationSame generic ecosystem
• HCL Hive is affected by a broken access control vulnerabilitySame generic ecosystem
• HCL Hive is affected by an information exposure vulnerabilitySame generic ecosystem
• WordPress Tonda theme < 2.6 - Local File Inclusion vulnerabilitySame generic ecosystem
• WordPress Tonda Core plugin < 2.6 - Local File Inclusion vulnerabilitySame generic ecosystem