CVE-2024-35663
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 HahnCreativeGroup WP Translate.This issue affects WP Translate: from n/a through 5.3.0.
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 WP Translate WordPress plugin allows users to perform actions beyond their intended privilege level, likely due to missing capability checks or nonce validation on sensitive functions within the plugin.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 WP Translate plugin is installedNavigate to WordPress admin > Plugins and look for 'WP Translate' in the list of installed plugins, or check the /wp-content/plugins/ directory for a folder named 'wp-translate' or similarAffected if The WP Translate plugin is installed and active
-
Check the installed plugin versionIn WordPress admin > Plugins > Installed Plugins, find WP Translate and note the version number displayedAffected if The installed version is older than the latest patched version (no specific version range provided; all versions may be affected)
-
Inspect plugin capabilities and user accessReview which user roles have access to the WP Translate plugin settings by checking the plugin menu visibility and any role-based access controls in the WordPress adminAffected if Non-administrator users (editors, authors, contributors, or subscribers) can access or modify WP Translate settings
-
Check for exposed admin AJAX or REST API endpointsExamine the plugin files (in wp-content/plugins/) for AJAX handlers (wp_ajax_) or REST API routes that process sensitive actions without capability checks, or use a web vulnerability scanner to probe /wp-admin/admin-ajax.php and /wp-json/ for WP Translate-related actionsAffected if The plugin exposes endpoints that process translation configuration or content changes without verifying user permissions
A user is affected if the WP Translate plugin is installed and non-administrator users can access or trigger sensitive plugin functions without proper authorization checks.
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 dataApply available vendor patches or update to the latest version of WP Translate. Until a patch is available, restrict plugin access to trusted administrators only and monitor for unauthorized configuration changes.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35663 — 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-35663 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