dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-58592

HIGH · 8.1 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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.10.2.

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 confidence

This is a PHP Object Injection vulnerability in the TranslatePress WordPress plugin caused by deserializing untrusted data. The flaw allows an attacker to inject malicious PHP objects, potentially leading to code execution, file operations, or other attacks depending on available classes in the application environment.

MitigationUpdate TranslatePress to the latest patched version. If no patch is available, disable the plugin until a fix is released, and review server-side deserialization endpoints for proper input validation.

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

CVSS:3.1/AV:N/AC:H/PR:N/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 TranslatePress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'TranslatePress' in the list. Alternatively, check the /wp-content/plugins/translatepress directory exists on the server.
    Affected if TranslatePress plugin is installed and active on the WordPress site
  2. Determine installed TranslatePress version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under TranslatePress. Alternatively, check the main plugin file header in /wp-content/plugins/translatepress/[plugin-file].php for the 'Version' tag.
    Affected if The installed version matches or falls within any affected version range published in the official CVE advisory (compare your version to the patched version)
  3. Check for evidence of deserialization exploitation
    Review WordPress debug logs (wp-content/debug.log if enabled), server access logs, and error logs for patterns involving unserialize(), PHP object injection attempts, or unusual PHP warnings related to object instantiation. Also check for new or modified PHP files in the plugin directory.
    Affected if Logs show deserialization function calls, PHP object injection warnings, or unexpected file modifications in the plugin directory
  4. Inspect WordPress audit logs for plugin-related activity
    Check WordPress activity logs or security plugins for suspicious user sessions, particularly actions involving the TranslatePress settings or translation functionality that might trigger deserialization endpoints.
    Affected if Unusual or unauthorized activity involving TranslatePress settings or translation save/load operations is present

You are affected if TranslatePress plugin is installed and your installed version falls within the affected version range stated in the official CVE advisory; additionally, watch for signs of deserialization exploitation in your logs.

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 TranslatePress to the latest patched version. If no patch is available, disable the plugin until a fix is released, and review server-side deserialization endpoints for proper input validation.

Recommended fix Moderate confidence

Latest TranslatePress version available (check vendor for 2.10.3 or higher that contains the security patch)

  1. Check the official TranslatePress plugin repository or vendor advisory for the latest version that includes the security fix for CVE-2025-58592
  2. Backup your WordPress site before performing any updates
  3. Update the TranslatePress plugin to the latest available version that addresses the deserialization vulnerability
  4. Verify the update was successful and test multilingual functionality

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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 locally
dbcve dependency scanner

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