Kama Click CounterWordPress extension · Wp Kama
CVE-2017-18615
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 kama-clic-counter plugin before 3.5.0 for WordPress has XSS.
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 kama-clic-counter WordPress plugin before version 3.5.0 contains a Cross-Site Scripting (XSS) vulnerability that could allow authenticated attackers to inject malicious scripts into web pages viewed by other users.
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
Kama Click CounterWordPress extension
< 3.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify kama-clic-counter plugin is installedNavigate to WordPress Admin Dashboard > Plugins. Look for 'Kama Click Counter' or 'kama-clic-counter' in the installed plugins list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'kama-clic-counter'.Affected if The plugin folder 'kama-clic-counter' exists in the plugins directory.
-
Determine installed plugin versionIn WordPress Admin > Plugins > Kama Click Counter, click on the plugin name to view details, or inspect the main plugin file (e.g., kama-clic-counter.php) and look for a 'Version:' comment in the file header.Affected if The version number displayed is lower than 3.5.0 (e.g., 3.4.0, 3.0.1, etc.).
-
Confirm plugin is activeIn WordPress Admin > Plugins, check if Kama Click Counter shows as 'Active' under the plugin status column. Inactive plugins typically cannot be exploited.Affected if The plugin is currently activated.
-
Verify authenticated user access existsReview WordPress user accounts in Admin > Users. The XSS vulnerability requires an authenticated attacker (any user role with access to the plugin functionality). Check if user accounts exist and whether multi-user access is possible.Affected if Multiple user accounts exist, or the site allows user registration, creating a scenario where one user could inject XSS for others to view.
A user is affected if the kama-clic-counter plugin is installed with a version lower than 3.5.0 and the plugin is active on a WordPress site that has multiple users or allows user registration.
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.
From vendor data3.5.0
Update the kama-clic-counter plugin to version 3.5.0 or later to remediate the XSS vulnerability.
Fix this in Kama Click Counter
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18615 — 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-18615 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