LiveActive security incident?Get immediate response
CVE Record

CVE-2025-69002: WordPress OneLife theme <= 3.9 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in designthemes OneLife onelife allows Object Injection.This issue affects OneLife: from n/a through <= 3.9.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-69002 affects the WordPress OneLife theme through version 3.9. It involves unsafe handling of serialized data, which can let an authenticated attacker inject PHP objects. The CVSS score is 8.8, reflecting potential confidentiality, integrity, and availability impact. Public sources do not show active exploitation or a confirmed fixed version.

Executive priority

Prioritize identification and remediation on externally reachable WordPress sites, especially those with user registration or many low-privilege users. Treat this as high severity, but not as confirmed actively exploited based on provided sources. If no fixed version exists, plan replacement or removal.

Technical view

The issue is CWE-502 deserialization of untrusted data in designthemes OneLife, package onelife, through <= 3.9. CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Exploitation is network-reachable, low complexity, requires low privileges, and requires no user interaction. Source details do not include vulnerable endpoints or gadget-chain specifics.

Likely exposure

Exposure is likely limited to WordPress sites with the OneLife theme installed, especially version 3.9 or earlier. Because the CVSS vector requires PR:L, sites allowing user registration or broad low-privilege access may face higher practical risk. Evidence is incomplete on whether inactive installations are exploitable.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The vulnerability requires an authenticated low-privilege attacker and no victim interaction. Public details are sparse, so exploitation feasibility may depend on site configuration and available PHP classes.

Researcher notes

Public sources identify the vulnerability class and affected version range but do not provide endpoint, parameter, proof-of-concept, fixed-version, or exploitation telemetry. Validate exposure conservatively and avoid assuming exploitability beyond authenticated object injection in OneLife <= 3.9.

Mitigation direction

  • Inventory WordPress sites for designthemes OneLife theme versions 3.9 or earlier.
  • Check vendor and Patchstack guidance for a fixed release or official mitigation.
  • Update the theme if a vendor-supported fixed version is available.
  • Remove or replace the theme where no supported fix is available.
  • Limit untrusted account creation and review low-privilege user access until resolved.

Validation and detection

  • Confirm OneLife theme name and version in WordPress admin or asset inventory.
  • Verify whether the installed version is 3.9 or earlier.
  • Review CVE and Patchstack records for current remediation status.
  • Check whether public registration or low-privilege accounts are enabled.
  • After remediation, confirm the vulnerable theme version is absent or updated.
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-69002 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-69002Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
designthemesOneLifeonelife, 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.