dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-30773

HIGH · 7.2 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Deserialization of Untrusted Data vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Object Injection.This issue affects TranslatePress: from n/a through <= 2.9.6.

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

A deserialization vulnerability in the TranslatePress multilingual WordPress plugin allows untrusted data to be processed through PHP's unserialize() function, enabling an attacker to inject arbitrary PHP objects. This could lead to code execution, database manipulation, or file system access depending on available classes in the application.

MitigationUpgrade to TranslatePress version 2.9.7 or later. If patching is not immediately possible, implement input validation at the application layer to sanitize data before deserialization.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm WordPress installation
    Check for the presence of wp-config.php or wp-login.php in the web root directory
    Affected if WordPress is not present, then the TranslatePress plugin cannot be used
  2. Identify TranslatePress plugin installation
    Check the wp-content/plugins directory for the translatepress-multilingual folder, or query the WordPress plugins database table
    Affected if The plugin directory or database entry is not found, the plugin is not installed
  3. Determine installed TranslatePress version
    Read the main plugin file (e.g., translatepress.php) header in wp-content/plugins/translatepress-multilingual to extract the Version field, or use wp plugin list via WP-CLI
    Affected if The version number is lower than 2.9.7 (e.g., 2.9.6, 2.8.x, earlier versions)
  4. Verify plugin is active
    Check WordPress options table for the active_plugins option, or use WP-CLI: wp plugin list --status=active --filter=name=translatepress
    Affected if The plugin is active and processing multilingual content translations

If WordPress is running with TranslatePress plugin version 2.9.6 or earlier and the plugin is active, the environment is affected by this deserialization vulnerability.

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

Upgrade to TranslatePress version 2.9.7 or later. If patching is not immediately possible, implement input validation at the application layer to sanitize data before deserialization.

Recommended fix High confidence

Upgrade to TranslatePress version 2.9.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the TranslatePress plugin (translatepress-multilingual)
  4. Check the current installed version (should be <= 2.9.6)
  5. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org or the TranslatePress official website
  6. Verify the update was successful and the new version is > 2.9.6

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30773 — 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-30773 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