LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54053: WordPress Groundhogg plugin <= 4.2.2 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in Adrian Tobey Groundhogg groundhogg allows Object Injection.This issue affects Groundhogg: from n/a through <= 4.2.2.

MediumCVSS 6.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-54053 affects the WordPress Groundhogg plugin through version 4.2.2. It involves unsafe deserialization that can allow PHP object injection. The listed score is medium, but impact is high if exploited. The source data says exploitation requires high privileges and difficult conditions, reducing immediate mass-exploitation risk.

Executive priority

Prioritize this after confirmed exploited or unauthenticated vulnerabilities, but do not ignore it. A compromised administrator or privileged account could turn this into high-impact site compromise. Remediation should be scheduled promptly for any business-critical WordPress site using Groundhogg.

Technical view

The issue is CWE-502, deserialization of untrusted data, in Adrian Tobey Groundhogg. CVSS 3.1 is 6.6: network reachable, high attack complexity, high privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on WordPress sites running the Groundhogg plugin at version 4.2.2 or earlier. The affected-version metadata in the bundle is limited and partly inconsistent, so teams should verify installed versions directly rather than rely only on inventory labels.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates an attacker would need high privileges and favorable conditions. Treat this as a serious post-authentication risk, not a confirmed internet-wide exploitation event.

Researcher notes

The source bundle identifies object injection but does not include a vulnerable code path, proof of concept, patch diff, or fixed version. Avoid assumptions about exploitability beyond the CVSS vector. Validate exposure through installed plugin versions and official vendor/Patchstack updates.

Mitigation direction

  • Inventory WordPress sites for the Groundhogg plugin and exact installed version.
  • Check Groundhogg vendor and Patchstack guidance for a fixed release or official mitigation.
  • Update the plugin according to official guidance when a fixed version is identified.
  • Restrict high-privilege WordPress accounts and enforce MFA where possible.
  • Disable or remove Groundhogg where it is not operationally required.

Validation and detection

  • Confirm whether any WordPress site runs Groundhogg version 4.2.2 or earlier.
  • Review plugin changelogs or vendor advisories before marking remediation complete.
  • Check administrative accounts for unnecessary privileges or weak authentication controls.
  • Look for unusual high-privilege WordPress activity on sites with affected versions.
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-54053 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
Medium
CVSS
6.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/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
6.6CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H0.75.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.6Medium
CVSS 3.1 vector shape for CVE-2025-54053Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/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
Adrian TobeyGroundhogggroundhogg, 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.