CVE-2024-43350
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in Propovoice Propovoice CRM.This issue affects Propovoice CRM: from n/a through 1.7.6.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 confidencePropovoice CRM versions up to 1.7.6.4 contain an Insecure Direct Object Reference (IDOR) vulnerability where an attacker can manipulate a user-controlled key (such as a record ID or parameter) to bypass authorization checks and access or modify data belonging to other users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify installed Propovoice CRM versionLocate the version number in the plugin header file (typically in the main plugin PHP file), WordPress plugin admin page, or check the plugin database settings where the version may be storedAffected if The installed version is 1.7.6.4 or any earlier version (1.x.x up to 1.7.6.4)
-
Confirm the plugin is activeVerify Propovoice CRM plugin is enabled and running on the WordPress site through the WordPress admin plugin list or by checking active plugins in the wp_options tableAffected if The plugin is active and the version falls within the affected range
-
Identify endpoints accepting user-controlled keysReview the application for URL parameters or API endpoints that accept record IDs, entity IDs, or other object references as user input (common patterns include ?id=123, ?record_id=456, or /wp-json/propovoice/v1/ endpoints with ID parameters)Affected if Such parameters exist and accept numeric or GUID identifiers without requiring explicit authorization validation for each request
-
Test for missing authorization on resource accessIf you have access to multiple user accounts, attempt to access or modify records belonging to one user while authenticated as a different user by manipulating the ID parameter value in the requestAffected if The application allows access to records owned by other users without proper ownership verification, indicating the IDOR vulnerability is present
You are affected if Propovoice CRM version 1.7.6.4 or any earlier 1.x version is installed and active, and the application exposes endpoints that accept user-controlled object identifiers without verifying the authenticated user has permission to access that specific resource.
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 server-side authorization validation for all requests that accept user-controlled keys, ensuring the authenticated user has permission to access the requested resource regardless of provided parameters.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43350 — 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-43350 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