dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-69404

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-20
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
Deserialization of Untrusted Data vulnerability in ThemeREX Extreme Store extremestore allows Object Injection.This issue affects Extreme Store: from n/a through <= 1.5.10.

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

A deserialization vulnerability in ThemeREX Extreme Store (versions up to 1.5.10) allows unauthenticated remote attackers to inject malicious PHP objects through untrusted serialized data, potentially leading to arbitrary code execution.

MitigationUpdate to the latest patched version of ThemeREX Extreme Store immediately; if no patch exists, disable the theme/plugin and implement WAF rules as a temporary measure while awaiting vendor fix.

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 Extreme Store installation
    Check wp-content/themes/ directory for a folder named 'extreme-store' or 'themerex-extreme-store', or look in wp-content/plugins/ if distributed as a plugin
    Affected if ThemeREX Extreme Store theme or plugin folder exists in the WordPress installation
  2. Determine installed version
    Open the main theme/plugin PHP file (often functions.php or the primary plugin file) and locate the version declaration in the header comments or a version constant
    Affected if Version is 1.5.10 or lower, or version line is missing/unreadable making comparison impossible
  3. Verify theme is active
    In WordPress admin, go to Appearance > Themes and check if Extreme Store is the active theme, or check wp_options table for current_theme option
    Affected if ThemeREX Extreme Store is currently activated on the WordPress site
  4. Assess exposure
    Confirm the site accepts unauthenticated requests (theme does not require login for certain AJAX or callback functions)
    Affected if The theme processes requests from unauthenticated users, which is the default for this theme based on the unauthenticated attack vector description

If ThemeREX Extreme Store is installed, active, and running version 1.5.10 or lower, the environment is vulnerable to unauthenticated deserialization attacks.

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 to the latest patched version of ThemeREX Extreme Store immediately; if no patch exists, disable the theme/plugin and implement WAF rules as a temporary measure while awaiting vendor fix.

Recommended fix Moderate confidence

ThemeREX Extreme Store version > 1.5.10 (latest available patched release)

  1. 1. Check the current version of the ThemeREX Extreme Store theme installed on your WordPress site
  2. 2. Navigate to Appearance > Themes in WordPress admin to confirm the installed version
  3. 3. Visit the official ThemeREX theme repository or contact ThemeREX support to obtain the latest patched version of Extreme Store
  4. 4. Before upgrading, create a complete backup of your WordPress site including database and files
  5. 5. Test the new theme version in a staging environment first if possible
  6. 6. Upload and activate the updated Extreme Store theme version
  7. 7. Verify that all site functionality works correctly after the upgrade
  8. 8. Monitor for any security-related updates and subscribe to theme update notifications
Caveat Check ThemeREX changelog for any template or functionality changes between your current version and the new version before upgrading in production

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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