dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-3953

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 – The Most Popular Privacy-Friendly Analytics Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'optionUpdater' function in all versions up to, and including, 14.13.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary plugin settings.

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 contains a Broken Access Control vulnerability in the 'optionUpdater' function. This function, responsible for updating plugin settings, lacks proper capability verification, allowing any authenticated user with Subscriber-level permissions or higher to modify arbitrary plugin options. An attacker could exploit this to change plugin configuration settings.

MitigationUpdate the WP Statistics plugin to version 14.14 or later, which includes proper capability checks on the optionUpdater function. Until patched, limit subscriber-level account creation and audit existing user roles.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Statistics, or check the plugin files in /wp-content/plugins/wp-statistics/ for the main PHP file and read its version header
    Affected if Plugin is installed and active
  2. Determine installed WP Statistics version
    Read the version number from the plugin's main PHP file header (e.g., wp-statistics.php) or from the WordPress plugins admin page
    Affected if Version is lower than 14.14 (the patched version)
  3. Check for WordPress user accounts with Subscriber role
    In WordPress admin, go to Users > All Users and review the Role column for accounts with Subscriber role, or query the wp_usermeta table for wp_capabilities containing 'subscriber'
    Affected if Any Subscriber-level accounts exist in the system
  4. Verify the optionUpdater function lacks capability checks
    Review the wp-statistics plugin code, specifically the optionUpdater function (typically in includes/functions/ or similar), and confirm it does not include current_user_can() or a capability check before processing options
    Affected if The optionUpdater function executes without capability verification (code inspection required)

User is affected if WP Statistics version is below 14.14 AND at least one Subscriber-level account exists, allowing unauthenticated or lower-privileged users to modify plugin settings via the optionUpdater function.

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 the WP Statistics plugin to version 14.14 or later, which includes proper capability checks on the optionUpdater function. Until patched, limit subscriber-level account creation and audit existing user roles.

Recommended fix Moderate confidence

WP Statistics version 14.13.4 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Statistics in the plugin list
  4. If an update is available, click 'Update Now' to install the latest version
  5. After updating, verify the plugin is running the newest release by checking the version number in the plugin details
  6. Confirm that the optionUpdater function now properly checks user capabilities before allowing settings modifications

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3953 — 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-2025-3953 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