Wp StatisticsWordPress extension · Veronalabs
CVE-2017-18515
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 · uneditedThe wp-statistics plugin before 12.0.8 for WordPress has SQL injection.
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-statistics WordPress plugin before version 12.0.8 contains a SQL injection vulnerability that allows attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling unauthorized data access or database manipulation.
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 StatisticsWordPress extension
< 12.0.8CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm wp-statistics plugin is installedAccess your WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named wp-statisticsAffected if The wp-statistics plugin folder exists in the WordPress plugins directory
-
Identify the installed versionIn the WordPress admin panel, find wp-statistics in the Plugins list and view the version number displayed, or open the main plugin file in the wp-statistics folder and locate the Version header in the plugin commentsAffected if A version number is displayed indicating the plugin is installed
-
Compare version against affected rangeCompare your installed version to the affected range: versions prior to 12.0.8 are vulnerableAffected if The installed version is lower than 12.0.8
-
Verify the plugin is activeCheck the Plugins page in WordPress admin to confirm wp-statistics is activatedAffected if The plugin is installed and currently active
If the wp-statistics plugin is installed with a version lower than 12.0.8 and is active, the environment is affected by this SQL injection vulnerability
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 · scoped12.0.8
Update the wp-statistics plugin to version 12.0.8 or later to remediate the SQL injection vulnerability.
WP Statistics 12.0.8
- Backup your WordPress database and files before making any changes
- Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- Find the WP Statistics plugin in the list
- Click Update Now or update to the latest version to get version 12.0.8 or later
- Alternatively, download version 12.0.8 from wordpress.org and upload it manually via Plugins > Add New > Upload Plugin
- Verify the plugin version after update to confirm 12.0.8 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Statistics
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18515 — 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-2017-18515 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