WP Statistics < 14.16.10 - Subscriber+ Sensitive Data Disclosure via Metabox AJAX Handlers

Why this deserves its current priority

CVSS is 6.5. 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 Unknown/WP Statistics (generic). Check affected ranges and fixed versions before updating.

Recommended response

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

Evidence timeline and material changes

1. Published upstream

   Aug 8, 2026

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

2. Source modified

   Aug 26, 2026

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

3. First seen by HOL

   Aug 8, 2026

Sources and claim methodology

• Source referencewpscan.com

Related CVEs

• Package URLs can be used to exfiltrate arbitrary INI file values and environment variablesAlso CWE-200
• WP-CRM System <= 3.4.6 - Authenticated (Contributor+) Exposure of Sensitive Information via 'contact_id' ParameterAlso CWE-200
• BM Content Builder < 3.17.1 - Authenticated (Subscriber+) Arbitrary File ReadSame generic ecosystem
• BM Content Builder < 3.17.1 - Authenticated (Subscriber+) Arbitrary File DeletionSame generic ecosystem
• Handily <= 1.0.3 - Missing Authorization to Unauthenticated Arbitrary Stripe Payment Settings Modification via 'stripe_publishbale_key' ParameterSame generic ecosystem
• Product Feed Manager for WooCommerce <= 6.6.43 - Authenticated (Shop Manager+) Path Traversal to File Deletion via 'provider' ParameterSame generic ecosystem