Visitor StatisticsWordPress extension · Codepress
CVE-2024-24867
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Osamaesh WP Visitor Statistics (Real Time Traffic).This issue affects WP Visitor Statistics (Real Time Traffic): from n/a through 6.9.4.
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 · moderate confidenceThe WP Visitor Statistics (Real Time Traffic) WordPress plugin versions through 6.9.4 contains an information disclosure vulnerability allowing unauthorized actors to access sensitive visitor data without authentication. The CVSS 7.5 score indicates complete confidentiality breach with no privileges required.
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
Visitor StatisticsWordPress extension
<= 6.9.4CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if the plugin is installedNavigate to WordPress admin > Plugins and look for 'WP Visitor Statistics (Real Time Traffic)' or 'Codepress Visitor Statistics' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Identify the installed versionIn the Plugins page, locate the plugin and view the version number displayed beneath the plugin nameAffected if Version number is 6.9.4 or lower
-
Verify plugin statusCheck whether the plugin is activated by looking at the plugin status in the WordPress admin Plugins listAffected if Plugin is installed and activated (the vulnerability is exploitable without authentication, so mere activation exposes data)
Your environment is affected if the Codepress Visitor Statistics plugin is installed with version 6.9.4 or lower and the plugin is active.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the plugin to the latest patched version immediately. If no patch is available, disable the plugin and seek alternative visitor statistics solutions. Consider implementing WAF rules as a temporary measure.
Latest available version (6.9.5 or newer)
- 1. Log in to your WordPress admin dashboard.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate the 'WP Visitor Statistics' or 'Visitor Statistics' plugin.
- 4. If an update is available, click 'Update Now' to install the latest version.
- 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually.
- 6. After updating, verify the plugin is functioning correctly and review any new settings for security best practices.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Visitor Statistics
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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