dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-60205

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Unauthenticated PHP Object Injection in ThemeREX Addons <= 2.36.1.1 versions.

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

Unauthenticated PHP Object Injection vulnerability in ThemeREX Addons plugin versions 2.36.1.1 and below. The vulnerability allows remote attackers to inject malicious PHP objects via unserialized user input, potentially leading to remote code execution without authentication.

MitigationUpdate ThemeREX Addons to a version newer than 2.36.1.1 immediately. If no patched version is available, disable or remove the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/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. Locate ThemeREX Addons plugin installation
    Search the web server's plugins directory for a folder named 'themrex-addons', 'trx-addons', or similar ThemeREX-related plugin directories. Common paths include /wp-content/plugins/ on WordPress installations.
    Affected if The plugin folder exists in the plugins directory.
  2. Determine installed plugin version
    Open the main plugin PHP file (usually index.php, themrex-addons.php, or trx-addons.php inside the plugin folder) and locate the plugin header comment containing 'Version:' or a version constant. Compare the version number to 2.36.1.1.
    Affected if The reported version is 2.36.1.1 or lower.
  3. Verify plugin is active
    Check if the plugin is currently enabled on the WordPress site. In WordPress admin, go to Plugins > Installed Plugins and confirm ThemeREX Addons shows as 'Active', or query the wp_options table for the active_plugins entry.
    Affected if The plugin is active and processing requests.
  4. Confirm PHP unserialize handling of user input
    Review the plugin code for usage of unserialize() function that processes input from $_GET, $_POST, $_COOKIE, or similar superglobals without prior sanitization. Look for any AJAX endpoints or REST routes that accept serialized data.
    Affected if The plugin processes unserialized user input from unauthenticated sources.

You are affected if ThemeREX Addons is installed, active, version 2.36.1.1 or below, and processes unserialized user input from unauthenticated requests.

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 ThemeREX Addons to a version newer than 2.36.1.1 immediately. If no patched version is available, disable or remove the plugin until a fix is released.

Recommended fix Moderate confidence

ThemeREX Addons version greater than 2.36.1.1 (latest available version)

  1. 1. Update ThemeREX Addons plugin to the latest available version from the WordPress plugin repository or ThemeREX official source.
  2. 2. If automatic updates are not enabled, manually download the latest version and upload it via WordPress admin > Plugins > Add New > Upload Plugin.
  3. 3. After updating, verify the plugin is functioning correctly and no custom functionality is broken.
  4. 4. Review site for any suspicious activity or unauthorized access that may have occurred prior to patching.
  5. 5. Consider implementing a Web Application Firewall (WAF) rule to block serialized data in HTTP requests as an additional hardening measure.
Caveat Minor - theme functionality may need verification after upgrade, but core functionality should remain compatible

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-60205 — 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-60205 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