LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69404: WordPress Extreme Store theme <= 1.5.10 - PHP Object Injection vulnerability

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-69404 is a critical vulnerability in the WordPress Extreme Store theme by ThemeREX. A remote unauthenticated attacker may be able to trigger unsafe PHP object deserialization, which can affect confidentiality, integrity, and availability. Public sources identify affected versions through 1.5.10, but do not name a fixed version or active exploitation.

Executive priority

Prioritize within the current emergency patch cycle for any public WordPress site using Extreme Store. The issue is critical by CVSS and requires no login, but evidence of active exploitation is not provided. If the theme is absent, business exposure is unlikely.

Technical view

The issue is CWE-502 deserialization of untrusted data in the Extreme Store WordPress theme package “extremestore.” The CVSS 3.1 score is 9.8: network-accessible, low complexity, no privileges, and no user interaction. Sources describe PHP object injection, which may become severe depending on available gadget chains in the WordPress environment.

Likely exposure

Exposure is likely limited to WordPress sites running the ThemeREX Extreme Store theme at version 1.5.10 or earlier. The source bundle does not identify vulnerable configurations beyond the affected theme and version range.

Exploitation context

The CVE record rates exploitation as remotely reachable without authentication or user interaction. CISA KEV status is false in the provided data, and no cited source states active exploitation. Public sources do not provide confirmed exploit details.

Researcher notes

Key gaps remain: public sources in the bundle do not name a fixed version, exploit maturity, vulnerable endpoint, or required gadget chain. Avoid assuming exploitation in the wild. Validation should focus on accurate theme inventory, version confirmation, and monitoring vendor/Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the Extreme Store theme and installed version.
  • If version is 1.5.10 or earlier, treat the site as high priority.
  • Check ThemeREX, Patchstack, and CVE references for fixed-version guidance.
  • If no fix is available, consider replacing or disabling the affected theme.
  • Back up affected sites before theme changes or updates.
  • Increase monitoring for suspicious WordPress requests and unexpected file or option changes.

Validation and detection

  • Confirm whether the active or installed theme is Extreme Store.
  • Record the exact theme version from WordPress administration or asset inventory.
  • Compare the version against the affected range: through 1.5.10.
  • Verify whether vendor or Patchstack guidance now lists a fixed version.
  • Review security monitoring for anomalous unauthenticated requests to affected sites.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-69404 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-69404Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ThemeREXExtreme Storeextremestore, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.