KivicareWordPress extension · Iqonic
CVE-2024-35659
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 · uneditedMissing Authorization vulnerability in Iqonic Design KiviCare kivicare-clinic-management-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects KiviCare: from n/a through <= 3.6.6.
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 confidenceMissing Authorization vulnerability in the KiviCare WordPress plugin allows attackers to access functionality or data without proper permission validation due to incorrectly configured access control security levels. This broken access control issue enables unauthorized users to perform actions or view data they should not have permission to access.
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
KivicareWordPress extension
<= 3.6.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 KiviCare plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'KiviCare' or 'Iqonic Kivicare'. Note the installed version number displayed.Affected if The plugin is installed and the version number is 3.6.4 or lower.
-
Check WordPress user roles with KiviCare accessNavigate to Users > All Users and review each user's assigned role. KiviCare may add custom roles like 'KiviCare Doctor', 'KiviCare Patient', or 'KiviCare Receptionist'.Affected if Users are assigned KiviCare-specific roles without understanding their permission scope.
-
Verify KiviCare user capabilities configurationUse a role management plugin or WP-CLI command 'wp user list --all' and 'wp role list' to enumerate all defined roles and their capabilities. Check if KiviCare custom roles exist.Affected if KiviCare custom roles exist with overly broad or undefined capability sets.
-
Inspect AJAX or API endpoints exposed by KiviCareReview the plugin directory for PHP files containing 'add_action' or 'do_action' calls with 'wp_ajax_' or 'wp_ajax_nopriv_' hooks. Check if any sensitive actions lack permission checks using 'current_user_can' or similar.Affected if Sensitive AJAX/API endpoints are accessible to unauthenticated users or lower-privileged roles without proper capability verification.
You are affected if the KiviCare plugin version is 3.6.4 or lower, especially if unauthenticated or low-privilege users can access KiviCare-specific functionality.
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 dataImplement proper authorization checks on all sensitive endpoints and functions, enforce role-based access control (RBAC) consistently throughout the application, and verify that user permissions are validated before executing any privileged operations.
Fix this in Kivicare
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35659 — 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-35659 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