CVE-2024-34763
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 Builder for WooCommerce reviews shortcodes – ReviewShort woo-product-reviews-shortcode.This issue affects Builder for WooCommerce reviews shortcodes – ReviewShort: from n/a through <= 1.01.5.
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 · high confidenceThis is a Missing Authorization vulnerability in the ReviewShort WooCommerce reviews shortcode plugin. The plugin fails to properly enforce authorization checks, potentially allowing unauthenticated or lower-privileged users to access functionality they should not have permission to use. The CVSS 5.3 score indicates the issue is exploitable over the network but likely has limited scope impact.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 ReviewShort plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'ReviewShort WooCommerce reviews shortcode' or check the wp-content/plugins directory for a reviewshort folderAffected if The plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin Plugins page, click on the plugin to view details and note the version number displayed, or inspect the plugin's main PHP file header for the Version tagAffected if The version cannot be determined or is older than the patched version
-
Identify accessible shortcode endpointsExamine the plugin files (typically in reviewshort.php or includes/*.php) for shortcode definitions using add_shortcode() and note the callback function namesAffected if Shortcodes are defined without capability checks (such as current_user_can() or wp_verify_nonce()) before performing actions
-
Check AJAX endpoints for authorizationSearch plugin files for wp_ajax_ and wp_ajax_nopriv_ action hooks; verify if nopriv hooks exist and whether they include proper permission checks before executing sensitive operationsAffected if AJAX endpoints accessible to unauthenticated users (wp_ajax_nopriv_) lack current_user_can() or nonce verification checks
-
Test unauthenticated shortcode accessAttempt to access any shortcode provided by the plugin (commonly [wc_reviews] or similar) via a logged-out browser request or curl command without providing authentication credentialsAffected if The shortcode renders content or executes functions without requiring login or verifying user capabilities
A user is affected if the ReviewShort plugin is installed and its shortcodes or AJAX endpoints respond to unauthenticated requests without verifying user permissions or capabilities.
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 dataUpdate to a patched version of the plugin if available. If no patch exists, implement proper capability checks and authorization validation within the plugin's shortcode handlers and any AJAX endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34763 — 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-34763 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