Skip to main content
Menu
CVEs

CVE

Groundhogg unauthenticated stored XSS via shortcode merge tag

Groundhogg through 4.10 is affected when a post title is rendered through the [ghr] shortcode after the post is published. No fixed version is listed.

CVE-2026-119635EUVD-2026-128550GHSA-XX63-WRMW-VP28Published Updated Summary written by a model

7.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: No fix is listed, so limit exposure by not rendering post titles through the [ghr] shortcode until a fixed version is released.

Summary

The Groundhogg plugin for WordPress has a stored cross-site scripting flaw that can be reached remotely, without logging in. An attacker can inject arbitrary scripts into pages that run in the browser of any user who opens an affected page.

Original description

The Groundhogg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_title' merge-tag of the [ghr] shortcode in versions up to, and including, 4.10 The post_title replacement is registered with 'nested' => true, so the nested branch of Replacements::do_replacement() returns the merge value through tackle_replacements() without passing it through escape_merge_tags()/escape_shortcodes(); the callback single_post() calls html_entity_decode(get_the_title(), ENT_QUOTES), converting the entity-encoded text that wp_filter_kses leaves intact on a Contributor's post title back into raw HTML, which is then emitted into the rendered post. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Who should check

Sites running Groundhogg where users with Contributor access can create posts whose titles are rendered through the [ghr] shortcode.

“Escape the {post_title} replacement so entity-encoded titles can't become live markup”

github.com

cve.now Index

29Pcve.now Index 29 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

What to do

  • Workaround: No fix is listed, so limit exposure by not rendering post titles through the [ghr] shortcode until a fixed version is released.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119635 (Groundhogg <= 4.10 - Unauthenticated Stored Cross-Site Scripting via 'post_title' Merge-Tag of [ghr] Shortcode), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119635 (entry last updated 2026-11-18):
Affected:
- trainingbusinesspros Groundhogg — AI CRM, Newsletters, and Marketing Automation: through 4.10
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The injected post title must be rendered through the [ghr] shortcode after the post is published. (source: https://github.com/groundhoggwp/groundhogg/commit/c324b315d2fad97484f85be61b547bf5d160a1f4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-119635 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119635 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/2763afc5-0c1c-4557-8638-4d0f61717a7a?source=cve
- https://plugins.trac.wordpress.org/browser/groundhogg/tags/4.10/includes/replacements.php#L2598
- https://plugins.trac.wordpress.org/browser/groundhogg/tags/4.10/includes/replacements.php#L1377
- https://plugins.trac.wordpress.org/browser/groundhogg/tags/4.10/includes/replacements.php#L507
- https://plugins.trac.wordpress.org/browser/groundhogg/tags/4.10/includes/shortcodes.php#L170
- https://plugins.trac.wordpress.org/browser/groundhogg/tags/4.10/includes/shortcodes.php#L33
- https://github.com/groundhoggwp/groundhogg/commit/c324b315d2fad97484f85be61b547bf5d160a1f4
- https://plugins.trac.wordpress.org/changeset/3806204/groundhogg/trunk/includes/replacements.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119635
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119635"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • trainingbusinesspros Groundhogg — AI CRM, Newsletters, and Marketing Automation

    through 4.10

Evidence 10

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119635

Is CVE-2026-119635 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Entity-encoded post titles are turned back into raw HTML when rendered through the [ghr] shortcode, so injected script can run in the rendered page.Source: github.com

Which versions are affected by CVE-2026-119635?

Groundhogg — AI CRM, Newsletters, and Marketing Automation: through 4.10.Source: cve.now feed data

Am I affected, and how do I check?

The listed range is Groundhogg 4.10 and earlier. The setup involves post titles rendered through the [ghr] shortcode after publication. To check a site's version, look at the Groundhogg version shown in the WordPress plugins screen.Source: github.com

How do I fix CVE-2026-119635?

No fixed version or vendor patch is listed in the checked facts, so no upgrade target can be given. Watch the vendor's advisory for an updated release.Source: github.com

What if there's no patch?

No fix is listed, so limit exposure by not rendering post titles through the [ghr] shortcode until a fixed version is released.Source: github.com

More CVEs