CVE-2025-10008
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 · uneditedThe Translate WordPress and go Multilingual – Weglot plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'clean_options' function in all versions up to, and including, 5.1. This makes it possible for unauthenticated attackers to delete limited transients that contain cached plugin options.
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 confidenceThe Weglot WordPress translation plugin has a broken access control vulnerability in the 'clean_options' function, missing a capability check that should verify user permissions before allowing deletion of transients. This enables unauthenticated attackers to delete certain cached plugin option transients, potentially causing denial of service or disruption to translation 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
- 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 Weglot plugin is installedCheck if the Weglot plugin directory exists in wp-content/plugins/ and identify the installed version from the plugin header or version fileAffected if Weglot plugin is present in the WordPress installation
-
Determine installed Weglot versionRead the version number from the plugin's main file (typically weglot.php) or the WordPress plugins admin pageAffected if Version is below 5.2.0 (the fixed version)
-
Confirm vulnerable endpoint accessibilityCheck if the WordPress AJAX endpoint (admin-ajax.php) is exposed and accessible without authentication - the clean_options function is hooked to a wp_ajax_ or wp_ajax_nopriv_ actionAffected if The AJAX endpoint handling clean_options is accessible to unauthenticated users (no capability check required)
-
Test transient deletion capabilityAttempt to delete Weglot transients via the plugin's AJAX action (if safely testing in a non-production environment) or review the registered AJAX hooks in the plugin code for wp_ajax_nopriv_ actions related to clean_optionsAffected if Transients can be deleted without authentication or capability verification
User is affected if Weglot plugin version is below 5.2.0 and the clean_options AJAX endpoint is accessible to unauthenticated users without permission 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.
dbcve · scopedUpdate the Weglot plugin to version 5.2 or later to receive the patched version that includes proper capability checks on the 'clean_options' function.
Version 5.2 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the Weglot Translate plugin
- If an update is available, click 'Update Now' to update to version 5.2 or later
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10008 — 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-2025-10008 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