dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3488

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WP Statistics plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 14.16.4. This is due to missing capability checks on multiple AJAX handlers including `wp_statistics_get_filters`, `wp_statistics_getPrivacyStatus`, `wp_statistics_updatePrivacyStatus`, and `wp_statistics_dismiss_notices`. These endpoints only verify a `wp_rest` nonce via `check_ajax_referer()` but do not enforce any capability checks such as `current_user_can()` or the plugin's own `User::Access()` method. Since the `wp_rest` nonce is available to all authenticated WordPress users, this makes it possible for authenticated attackers, with Subscriber-level access and above, to access sensitive analytics data (user IDs, usernames, emails, visitor tracking data), retrieve and modify privacy audit compliance status, and dismiss administrative notices.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Statistics plugin for WordPress versions up to 14.16.4 lacks capability checks on multiple AJAX endpoints that only verify a wp_rest nonce. Since this nonce is accessible to all authenticated users (Subscriber-level and above), any logged-in user can access sensitive analytics data including user IDs, usernames, emails, and visitor tracking, modify privacy compliance status, and dismiss admin notices without proper authorization.

MitigationUpdate WP Statistics to version 14.16.5 or later which includes proper capability checks (e.g., current_user_can('manage_options')) on the affected AJAX handlers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Statistics plugin is installed
    Check WordPress plugins directory or admin panel for WP Statistics plugin. In filesystem, look in wp-content/plugins/wp-statistics/ for the main plugin file and read its version header.
    Affected if Plugin is installed and version is 14.16.4 or lower
  2. Confirm installed version number
    Read version from plugin header comment in wp-statistics.php or from WordPress admin plugin list. Compare against affected range: versions 14.16.4 and below are vulnerable.
    Affected if Installed version is 14.16.4 or lower
  3. Identify authenticated user roles present
    Check WordPress user roles under Users > All Users. Look for Subscriber-level or other low-privilege roles that have wp_rest nonce access.
    Affected if Any authenticated role (Subscriber or above) exists on the site
  4. Test AJAX endpoint access with low-privilege user
    Using a Subscriber-level test account, send a request to affected AJAX endpoints (such as wp-json/wp_statistics/v2/analytics or similar user data endpoints) with only a valid wp_rest nonce. Verify if sensitive data (user IDs, emails, analytics) is returned without capability check failure.
    Affected if AJAX endpoints return sensitive data or allow configuration changes without administrator-level capability verification

Your environment is affected if WP Statistics plugin version 14.16.4 or lower is installed AND any authenticated user role (Subscriber or above) exists on the site, allowing unauthorized access to sensitive analytics and admin functions via AJAX endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Statistics to version 14.16.5 or later which includes proper capability checks (e.g., current_user_can('manage_options')) on the affected AJAX handlers.

Recommended fix High confidence

Version 14.16.5 or later (any stable release newer than 14.16.4)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP Statistics plugin
  4. Click 'Update now' if an update is available, or manually download a version newer than 14.16.4 from the WordPress plugin repository
  5. Verify the update was successfully applied by checking the plugin version
Caveat Review plugin settings after upgrade as a precaution; no major breaking changes expected for this security patch

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3488 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3488 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data