CVE-2024-38790
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Smartsupp Smartsupp – live chat, chatbots, AI and lead generation smartsupp-live-chat allows Cross Site Request Forgery.This issue affects Smartsupp – live chat, chatbots, AI and lead generation: from n/a through <= 3.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Smartsupp WordPress plugin (versions through 3.6) allows attackers to trick authenticated users into performing unintended actions via malicious crafted requests.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Locate Smartsupp plugin installationCheck if the Smartsupp plugin directory exists in your WordPress installation at wp-content/plugins/smartsupp-live-chat/ or search for 'smartsupp' in the wp-content/plugins folderAffected if The Smartsupp plugin directory is present on the server
-
Identify installed versionOpen the main plugin file (usually smartsupp.php) and look for the 'Version' header in the plugin comment block, or check the WordPress admin under Plugins > Installed Plugins > Smartsupp Live ChatAffected if The displayed version is 3.6 or lower
-
Confirm plugin is activeLog in to WordPress admin and verify Smartsupp Live Chat shows as 'Active' under Plugins > Installed Plugins, or query the wp_options table for option_name 'active_plugins' containing 'smartsupp'Affected if The plugin is active and processing requests
-
Verify authenticated sessions existCSRF requires a logged-in user session; check if any user roles (administrator, editor, author, etc.) have active sessions on the WordPress siteAffected if Users are logged in and have session cookies for the site
-
Assess state-changing operationsReview plugin functionality for any actions that modify data such as settings changes, account configuration, or chat widget modifications - these would be the targets of CSRF attacksAffected if The plugin has configuration options or settings that can be changed via HTTP requests
Your environment is affected if the Smartsupp plugin versions 3.6 or below is installed and active on your WordPress site, and users can be authenticated while the plugin handles state-changing requests without CSRF token validation.
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 anti-CSRF tokens on state-changing operations and validate request origin headers (Referer/Origin) to prevent forged requests from malicious sites.
- 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-38790 — 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-38790 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