CVE-2024-31358
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 Saleswonder Team: Tobias 5 Stars Rating Funnel 5-stars-rating-funnel.This issue affects 5 Stars Rating Funnel: from n/a through <= 1.2.67.
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 5 Stars Rating Funnel WordPress plugin allows attackers to bypass access controls and perform actions they shouldn't be permitted to perform. The plugin fails to verify user capabilities before executing sensitive operations, allowing unauthenticated or low-privilege users to access restricted functionality.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > 5 Stars Rating Funnel and note the version number displayed, or query the plugin header via wp-cli: wp plugin list --name='5-stars-rating-funnel' --format=jsonAffected if The installed version falls within any vulnerable version range (compare against official security advisory)
-
Inspect plugin AJAX handlers for capability checksLocate the plugin's main PHP file and review all add_action() calls registering AJAX hooks (wp_ajax_*) and public hooks (wp_ajax_nopriv_*). For each handler, verify the code calls current_user_can() or a similar capability check before executing sensitive operationsAffected if AJAX handlers lack current_user_can() verification and allow unauthenticated (nopriv) or low-privilege access
-
Review admin action handlers for authorizationExamine all admin-facing functions hooked to admin_init, admin_post_, or similar admin actions. Check if each function validates user capabilities using current_user_can() before processing data or modifying settingsAffected if Admin actions execute without capability verification, allowing lower-privilege users to trigger restricted functions
-
Check for unprotected sensitive functionsSearch the plugin source for functions that modify ratings, funnel settings, or user data. Locate where these functions are called and verify they are wrapped with current_user_can() checks or called only from properly protected hooksAffected if Sensitive operations (modifying ratings, funnel configuration, exporting data) can be invoked without verifying user permissions
-
Verify nonce implementation on sensitive operationsSearch the plugin code for wp_nonce_field(), wp_verify_nonce(), or check_admin_referer() calls adjacent to sensitive operations. Confirm nonces are present on all forms and AJAX requests handling funnel or rating dataAffected if Sensitive operations lack nonce verification, allowing CSRF attacks in addition to authorization bypasses
A user is affected if the installed version is within the vulnerable range AND the plugin lacks capability checks (current_user_can()) on sensitive AJAX, admin, or data-modification functions.
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 capability checks using WordPress functions like current_user_can() and add nonce verification on all admin-facing and sensitive operations. Update to the latest patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31358 — 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-31358 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