LiveActive security incident?Get immediate response
CVE Record

CVE-2025-53299: WordPress ThemeMakers Visual Content Composer Plugin <= 1.5.8 - PHP Object Injection Vulnerability

Deserialization of Untrusted Data vulnerability in ThemeMakers ThemeMakers Visual Content Composer tmm_content_composer allows Object Injection.This issue affects ThemeMakers Visual Content Composer: from n/a through <= 1.5.8.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A critical flaw in the WordPress ThemeMakers Visual Content Composer plugin can let an unauthenticated attacker trigger unsafe PHP object deserialization. In business terms, exposed WordPress sites using versions up to 1.5.8 may face full site compromise risk. The provided sources do not confirm active exploitation or a fixed version.

Executive priority

Prioritize same-day triage for public WordPress sites. If the plugin is present at an affected version, removal or verified remediation should be treated as critical because the stated impact includes confidentiality, integrity, and availability loss.

Technical view

CVE-2025-53299 is CWE-502 deserialization of untrusted data in ThemeMakers Visual Content Composer package tmm_content_composer through version 1.5.8. CVSS 3.1 is 9.8 with network access, low complexity, no privileges, and no user interaction. Source details do not include vulnerable endpoint, proof of concept, or confirmed patch.

Likely exposure

Exposure is likely limited to WordPress sites with ThemeMakers Visual Content Composer installed, especially versions <= 1.5.8. The bundle lists default status as unaffected outside the named affected product and version range. Confirm plugin presence directly; do not infer exposure from WordPress use alone.

Exploitation context

The CVSS vector supports unauthenticated remote exploitability in principle, but the bundle does not provide exploit mechanics. KEV is false, and no cited source in the bundle states active exploitation. Treat as urgent because object injection can become severe when exploitable gadget chains exist.

Researcher notes

The source bundle is strong on affected product, weakness class, and CVSS, but sparse on exploit details and remediation. Validate exposure without relying on exploit reproduction. PHP object injection impact may depend on reachable code paths and available gadget chains in the target environment.

Mitigation direction

  • Inventory WordPress sites for ThemeMakers Visual Content Composer.
  • Disable or remove affected versions if business impact allows.
  • Check Patchstack and vendor guidance for a fixed version.
  • Update only to a confirmed safe release when available.
  • Increase monitoring for unusual WordPress request patterns.

Validation and detection

  • Confirm whether tmm_content_composer is installed on each WordPress site.
  • Record the installed plugin version and compare against <= 1.5.8.
  • Check asset inventories for externally reachable WordPress instances.
  • Review security logs for suspicious requests targeting WordPress plugin paths.
  • Document compensating controls if immediate removal is not possible.
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-53299 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-53299Attack 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
ThemeMakersThemeMakers Visual Content Composertmm_content_composer, 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.