CVE-2024-38792
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 ConveyThis Translate Team Language Translate Widget for WordPress – ConveyThis allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Language Translate Widget for WordPress – ConveyThis: from n/a through 234.
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 ConveyThis WordPress plugin allows attackers to access functionality not properly constrained by Access Control Lists (ACLs). The plugin fails to verify user permissions before executing certain actions, enabling unauthorized users to potentially perform operations that should require higher privileges. This is a broken access control (IDOR) vulnerability affecting versions through 234.
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.
-
Verify ConveyThis plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'conveythis-translator' or similar ConveyThis-related folder, or query the wp_options table for active plugins containing 'conveythis'.Affected if The ConveyThis plugin folder exists in the WordPress installation.
-
Identify installed ConveyThis versionOpen the main plugin file (usually conveythis-translator.php or similar) and locate the version comment/header, or check the WordPress plugins admin page for the installed version number.Affected if The installed version is 234 or lower.
-
Confirm plugin is activeCheck WordPress admin under Plugins > Installed Plugins to verify ConveyThis is activated, or query the wp_options table where option_name = 'active_plugins' and the result contains 'conveythis'.Affected if The plugin shows as 'Active' in WordPress.
-
Check for low-privileged user accountsReview WordPress user roles under Users > All Users and identify any accounts with roles below Administrator (such as Editor, Author, Contributor, or Subscriber).Affected if There are non-Administrator user accounts registered on the site.
A user is affected if they have ConveyThis plugin version 234 or lower installed and active on their WordPress site, regardless of whether low-privileged users exist on the system.
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 (e.g., current_user_can()) and authorization validation on all sensitive functions and AJAX endpoints within the plugin to ensure only users with appropriate privileges can access protected functionality.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38792 — 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-38792 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