LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68899: WordPress Vivagh theme <= 2.4 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in designthemes Vivagh vivagh allows Object Injection.This issue affects Vivagh: from n/a through <= 2.4.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-68899 affects the WordPress Vivagh theme through version 2.4. It is a high-severity PHP object injection issue. An attacker with low-level site access could potentially affect data confidentiality, integrity, or availability. No public source provided here confirms active exploitation.

Executive priority

Treat as a near-term remediation item for any site using Vivagh. The issue is high severity, but urgency depends on confirmed use of the theme and whether untrusted users can authenticate.

Technical view

The issue is CWE-502, deserialization of untrusted data, in designthemes Vivagh. CVSS 3.1 is 8.8 with network access, low complexity, low privileges required, and no user interaction. Impact ratings are high for confidentiality, integrity, and availability. Public details are limited to the CVE and Patchstack entry.

Likely exposure

Exposure is likely limited to WordPress sites running the Vivagh theme version 2.4 or earlier. Risk is higher where low-privileged accounts can log in or be created by external users.

Exploitation context

The CVSS vector indicates exploitation is network-accessible and requires low privileges, not user interaction. The CVE is not listed as KEV in the provided data, and the sources do not confirm active exploitation or public exploit availability.

Researcher notes

The public record identifies unsafe deserialization leading to PHP object injection, but does not provide technical trigger details in the supplied sources. Avoid assuming remote code execution unless supported by a vendor advisory or further validated evidence.

Mitigation direction

  • Inventory WordPress sites for the Vivagh theme and version.
  • Check the vendor and Patchstack entry for an official patched version.
  • Update the theme if a fixed release is available.
  • If no fix is available, consider removing or replacing the theme.
  • Limit creation and use of low-privileged WordPress accounts.
  • Monitor WordPress logs for unusual authenticated activity.

Validation and detection

  • Confirm whether Vivagh is installed on each WordPress site.
  • Record the installed Vivagh version and compare it to 2.4 or earlier.
  • Review user registration and low-privileged account exposure.
  • Check vulnerability scanners or Patchstack data for site-specific detection.
  • Document remediation status for each affected site.
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-68899 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-68899Attack 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
designthemesVivaghvivagh, 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.