LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54686: WordPress Exertio Theme <= 1.3.2 - PHP Object Injection Vulnerability

Deserialization of Untrusted Data vulnerability in scriptsbundle Exertio exertio allows Object Injection.This issue affects Exertio: from n/a through <= 1.3.2.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-54686 is a critical WordPress theme issue in scriptsbundle Exertio through version 1.3.2. The reported flaw can allow PHP object injection through unsafe deserialization, potentially affecting confidentiality, integrity, and availability. The provided sources do not confirm active exploitation or name a fixed version.

Executive priority

Treat this as urgent for any internet-facing WordPress property running Exertio. The severity is critical, but business urgency depends on whether the theme is present and reachable in production.

Technical view

The vulnerability is CWE-502, deserialization of untrusted data, in the Exertio WordPress theme. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Sources do not document the vulnerable endpoint, exploitation prerequisites beyond CVSS, gadget chain, or patch details.

Likely exposure

Public WordPress sites using the Exertio theme version 1.3.2 or earlier are the likely exposure group. Confirm exposure from deployed theme inventory rather than assuming all WordPress sites are affected.

Exploitation context

The CVSS vector indicates unauthenticated remote reachability without user interaction. However, KEV is false and the provided sources do not cite active exploitation, public exploit availability, or weaponized details.

Researcher notes

The source bundle lacks endpoint-level detail, proof-of-concept status, patch version, and exploitation evidence. Validation should focus on asset inventory, version confirmation, and vendor advisory tracking, not speculative exploit testing.

Mitigation direction

  • Inventory WordPress sites for the Exertio theme and exact version.
  • Check scriptsbundle and Patchstack guidance for a fixed release or mitigation.
  • Upgrade if a vendor-supported fixed version is available.
  • Disable or remove Exertio where no acceptable fix is available.
  • Prioritize backups and monitoring before remediation on production sites.

Validation and detection

  • Confirm whether Exertio is installed or active on each WordPress site.
  • Record the deployed Exertio version and compare with <= 1.3.2.
  • Review vendor or Patchstack notes for affected configurations.
  • Check web logs for suspicious requests to Exertio theme paths.
  • Verify remediation by confirming the theme is upgraded, disabled, or removed.
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-54686 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-54686Attack 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
scriptsbundleExertioexertio, 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.