Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10008: CWE-862 Missing Authorization in remyb92 Translate WordPress and go Multilingual – Weglot

0
Medium
VulnerabilityCVE-2025-10008cvecve-2025-10008cwe-862
Published: Thu Oct 30 2025 (10/30/2025, 05:28:27 UTC)
Source: CVE Database V5
Vendor/Project: remyb92
Product: Translate WordPress and go Multilingual – Weglot

Description

The 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.

AI-Powered Analysis

AILast updated: 10/30/2025, 06:22:19 UTC

Technical Analysis

CVE-2025-10008 identifies a missing authorization vulnerability (CWE-862) in the Translate WordPress and go Multilingual – Weglot plugin, a widely used WordPress plugin for website translation. The vulnerability exists in the 'clean_options' function, which lacks proper capability checks before allowing deletion of cached plugin options stored as transients. This flaw permits unauthenticated attackers to remotely invoke this function and delete limited transient data without any authentication or user interaction. The transient data typically caches plugin options to optimize performance; its deletion can cause temporary loss of cached settings, forcing the plugin to regenerate or reload options, potentially disrupting translation services or causing inconsistent behavior. The vulnerability affects all versions up to and including 5.1. The CVSS v3.1 base score is 5.3 (medium), reflecting network attack vector, no privileges required, no user interaction, and limited impact on integrity without affecting confidentiality or availability. No patches or exploits are currently reported, but the vulnerability's presence in a popular plugin increases the risk of future exploitation. The issue highlights the importance of enforcing authorization checks on sensitive plugin functions that modify or delete configuration data.

Potential Impact

For European organizations, the primary impact is on the integrity of multilingual website content management. Deletion of cached plugin options can lead to inconsistent translation behavior, degraded user experience, and potential administrative overhead to restore normal operation. While it does not directly compromise sensitive data or availability, the disruption of translation services can affect customer engagement, especially for e-commerce, government, or public service websites relying on multilingual support. Organizations with high traffic or regulatory requirements for accessibility and localization may face reputational damage or compliance challenges if translation services are impaired. Additionally, repeated exploitation could be used as a vector for denial of service by forcing constant cache regeneration. Since the vulnerability requires no authentication and can be triggered remotely, the attack surface is broad, increasing risk for websites exposed to the internet. European entities using the Weglot plugin should prioritize assessment and remediation to maintain service integrity.

Mitigation Recommendations

1. Monitor official Weglot plugin channels for security updates and apply patches promptly once released to fix the missing authorization check. 2. Until patches are available, restrict access to WordPress administrative endpoints and plugin functions via web application firewalls (WAF) or IP whitelisting to limit exposure. 3. Implement strict WordPress user role management to minimize unnecessary permissions and audit plugin usage regularly. 4. Enable detailed logging and monitoring of transient deletions or unusual plugin behavior to detect potential exploitation attempts early. 5. Consider temporarily disabling or replacing the Weglot plugin with alternative translation solutions if risk tolerance is low and patching is delayed. 6. Conduct security awareness training for site administrators to recognize and respond to anomalies in plugin performance or site translations. 7. Review and harden WordPress security configurations, including limiting REST API access and disabling unused endpoints that could be leveraged in attacks.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-09-04T21:45:42.043Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69030287a36935f672017491

Added to database: 10/30/2025, 6:15:35 AM

Last enriched: 10/30/2025, 6:22:19 AM

Last updated: 10/30/2025, 2:09:33 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats