dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-8425

HIGH · 8.8 CVSS v3.1 Published 2025-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The My WP Translate plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the ajax_import_strings() function in all versions up to, and including, 1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 confidence

The My WP Translate WordPress plugin has a missing capability check on the ajax_import_strings() function, allowing authenticated users with Subscriber-level access to update arbitrary WordPress options via AJAX. Attackers can modify the default registration role to Administrator and enable user registration, creating an administrative account and achieving full site compromise.

MitigationUpdate the plugin to a patched version once available, or implement proper capability checks (e.g., current_user_can('manage_options')) on the ajax_import_strings() function to verify admin-level permissions before allowing option modifications.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify My WP Translate plugin is installed
    Check your WordPress installation under wp-content/plugins/ for a folder named 'my-wp-translate' or view the installed plugins list in WP Admin > Plugins
    Affected if The plugin folder or listing exists in your WordPress installation
  2. Determine the installed plugin version
    In WP Admin, go to Plugins > My WP Translate and read the version number from the plugin description, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if You cannot determine the version or the version is unknown compared to any patched release
  3. Confirm if user registration is enabled
    In WordPress Admin, go to Settings > General and check the box labeled 'Anyone can register' - verify this setting was not intentionally enabled by an administrator
    Affected if User registration is enabled but was not deliberately set by an administrator
  4. Check the default user role setting
    In WordPress Admin, go to Settings > General and examine the 'Default Role' dropdown - look for 'Administrator' or any role that was not intentionally set
    Affected if Default role is set to Administrator or a high-privilege role without explicit administrator action
  5. Audit user accounts for unauthorized administrators
    In WordPress Admin, go to Users > All Users and review the list for any administrator accounts that are unknown, unexpected, or were created recently
    Affected if Unexpected administrator-level accounts exist in the user list

If the My WP Translate plugin is present and you find user registration enabled, a changed default role, or unauthorized admin accounts, the vulnerability has likely been exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version once available, or implement proper capability checks (e.g., current_user_can('manage_options')) on the ajax_import_strings() function to verify admin-level permissions before allowing option modifications.

Recommended fix Moderate confidence

Version 1.2 or later (check wordpress.org/plugins/my-wp-translate/ for current stable release)

  1. 1. Navigate to WordPress admin dashboard > Users > Registration Settings
  2. 2. Ensure 'Anyone can register' is unchecked (disable if enabled by attacker)
  3. 3. Set 'Default New User Role' to 'Subscriber' (or lowest privilege role), not 'Administrator'
  4. 4. If you have file system access, navigate to wp-content/plugins/my-wp-translate/
  5. 5. Rename the plugin folder (e.g., my-wp-translate-disabled) to disable it temporarily
  6. 6. Check for a newer version of My WP Translate plugin at wordpress.org/plugins/my-wp-translate/
  7. 7. If version 1.2 or higher is available, install the update from the WordPress plugin repository
  8. 8. After updating, re-enable user registration settings only if required for site functionality
Caveat Minor - plugin should continue functioning normally after upgrade; review translation imports after patching

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8425 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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