dbcve.org
Wp Online Users StatsWordPress extension · Hk1993

CVE-2025-4966

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to after 1.0.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Online Users Stats plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing nonce validation within the hk_dataset_results() function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Online Users Stats WordPress plugin lacks nonce validation in its hk_dataset_results() function, allowing unauthenticated attackers to forge administrative requests. By tricking a site admin into clicking a malicious link, attackers can inject arbitrary web scripts that execute in the admin's browser session.

MitigationUpdate to a patched version when available, or add WordPress nonce verification to the hk_dataset_results() function to validate request authenticity before processing.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Online Users StatsWordPress extension
Affected:<= 1.0.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Confirm plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Online Users Stats' or 'Hk1993 Wp Online Users Stats'. Alternatively, check the /wp-content/plugins/ directory for a folder named similar to 'wp-online-users-stats' or 'hk-online-users-stats'.
    Affected if The plugin is not installed on the WordPress site
  2. Identify installed version
    In WordPress admin, find the plugin in the Plugins list and check the version number displayed beneath the plugin name. Or open the main plugin PHP file (usually named index.php or the plugin slug) and look for a Version header in the plugin comments at the top.
    Affected if The installed version is 1.0.0 or any version below it (the affected range is <= 1.0.0)
  3. Locate the vulnerable function
    Using a file manager or FTP, navigate to the plugin directory and search for the function 'hk_dataset_results' in the PHP files. Common paths: /wp-content/plugins/wp-online-users-stats/ or similar.
    Affected if The function hk_dataset_results() exists in the plugin code
  4. Check for nonce validation
    Open the PHP file containing hk_dataset_results() and examine the function code. Look for calls to wp_verify_nonce(), check_admin_referer(), or nonce verification within the function.
    Affected if No nonce verification (such as wp_verify_nonce or check_admin_referer) is present in the hk_dataset_results() function

A site is affected if the WP Online Users Stats plugin is installed with version 1.0.0 or lower AND the hk_dataset_results() function lacks WordPress nonce verification.

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
Upgrade available Upgrade to a release after 1.0.0
Interim mitigation

Update to a patched version when available, or add WordPress nonce verification to the hk_dataset_results() function to validate request authenticity before processing.

Recommended fix Moderate confidence

Version 1.0.1 or later (check wordpress.org for current stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'WP Online Users Stats' in the plugin list
  4. Check if an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update appears, manually download the latest version from wordpress.org/plugins/wp-online-users-stats/ and reinstall

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

Fix this in Wp Online Users Stats Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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