CVE-2026-16562

Statistics <= 14.16.9 - Authenticated (Subscriber+) Information Exposure

2026-08-03 00:00

Strategic Overview

Status: Patched in 14.16.10
Affected Plugin: WP Statistics – Simple, privacy-friendly Google Analytics alternative
Affected Version: <= 14.16.9
CVSS: 4.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2026-16562

View all WP Statistics – Simple, privacy-friendly Google Analytics alternative vulnerabilities

At a glance

CVE-2026-16562 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Statistics WordPress plugin, affecting versions <= 14.16.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 14.16.10; sites on affected versions should update now. Disclosed August 2026, reported by Shivamani Vastrala.

Vulnerability Overview

The Statistics plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 14.16.9. This is due to missing capability check in the BaseMetabox AJAX handler before returning statistics data. This makes it possible for authenticated attackers, with subscriber-level access and above, to access sensitive site statistics data by calling metabox AJAX handlers without the required capability.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in WP Statistics <= 14.16.9 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP Statistics the fix is 14.16.10: builds <= 14.16.9 are affected, anything from 14.16.10 onward is not.

Remediation

Update to version 14.16.10, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WP Statistics 14.16.10 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-16562 https://www.wordfence.com/threat-intel/vulnerabilities/id/762be203-b4bb-4618-9916-1ed4f33dbe2e https://nvd.nist.gov/vuln/detail/CVE-2026-16562

Related records

Same weakness class

4.3WP Statistics <= 13.2.5 Information Disclosure

Other vulnerabilities in WP Statistics – Simple, privacy-friendly Google Analytics alternative

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/