LiveActive security incident?Get immediate response
CVE Record

CVE-2024-37235: WordPress Groundhogg plugin <= 3.4.2.3 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Adrian Tobey Groundhogg groundhogg allows Cross Site Request Forgery.This issue affects Groundhogg: from n/a through <= 3.4.2.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-37235 is a CSRF issue in the WordPress Groundhogg plugin through version 3.4.2.3. An attacker could potentially cause a logged-in user to perform an unintended action, affecting integrity. The public bundle does not identify the exact action, a fixed version, or active exploitation.

Executive priority

Treat as a moderate-priority WordPress plugin exposure. Prioritize inventory and version verification because vulnerable internet-facing WordPress sites can be common, but the cited impact is limited to low integrity and requires user interaction.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in Adrian Tobey Groundhogg, package groundhogg, affecting versions through 3.4.2.3. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running the Groundhogg plugin at version 3.4.2.3 or earlier. Sites without this plugin, or running versions outside the affected range, are not indicated as affected by the supplied sources.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation would require user interaction, consistent with CSRF, but the bundle does not disclose the targeted function or business action.

Researcher notes

The public bundle lacks the vulnerable endpoint/action, proof details, fixed version, and mitigation specifics. Avoid assuming broader impact. Validation should focus on asset/version exposure and tracking vendor advisory updates rather than attempting exploit reproduction.

Mitigation direction

  • Inventory WordPress sites for the Groundhogg plugin and recorded version.
  • Review Groundhogg and Patchstack guidance for fixed versions or workarounds.
  • Update Groundhogg if the vendor provides a fixed release.
  • Temporarily disable Groundhogg where risk is unacceptable and business impact is manageable.
  • Reassess administrative workflows that rely on trusted logged-in browser sessions.

Validation and detection

  • Confirm whether Groundhogg is installed on each WordPress property.
  • Verify installed Groundhogg versions are not 3.4.2.3 or earlier.
  • Check vendor and Patchstack advisory pages for updated remediation details.
  • Review logs for unusual Groundhogg-related administrative changes around the disclosure window.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2024-37235 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-37235Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
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-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.