dbcve.org
Grand ConferenceWordPress extension · Themegoods

CVE-2025-64224

HIGH · 7.1 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 2.6.4 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ThemeGoods Grand Conference Theme Custom Post Type grandconference-custom-post allows Reflected XSS.This issue affects Grand Conference Theme Custom Post Type: from n/a through < 2.6.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Reflected XSS vulnerability in the Grand Conference WordPress theme's custom post type (grandconference-custom-post) allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in web pages.

MitigationUpdate the Grand Conference theme to version 2.6.4 or later which should contain proper input sanitization. Until patched, avoid clicking untrusted links to the affected site.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Grand ConferenceWordPress extension
Affected:< 2.6.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Grand Conference theme is installed
    Access WordPress admin dashboard, go to Appearance > Themes, or check /wp-content/themes/ directory for grandconference folder
    Affected if The Grand Conference theme by Themegoods is present on the WordPress site
  2. Determine installed theme version
    Check theme styles.css file in /wp-content/themes/grandconference/ for 'Version:' header, or view theme details in WordPress admin under Appearance > Themes
    Affected if Version number is displayed as less than 2.6.4 (e.g., 2.6.3, 2.6.0, 1.x.x, etc.)
  3. Confirm vulnerable custom post type exists
    Check if 'grandconference-custom-post' post type is registered by querying /wp-json/wp/v2/types or accessing potential endpoints that use this custom post type
    Affected if The custom post type 'grandconference-custom-post' is registered and accessible on the site
  4. Verify reflection point is reachable
    Attempt to access pages rendering the custom post type content and inspect if URL parameters are reflected in the page output without sanitization
    Affected if User-supplied input in URL parameters (such as in archive or single post views) is reflected back in the HTML output unsanitized

A site is affected if the Grand Conference theme version is below 2.6.4 AND the grandconference-custom-post custom post type is active and accessible, allowing unsanitized user input to be reflected in page output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.4 or later
Fixed in 2.6.4
Interim mitigation

Update the Grand Conference theme to version 2.6.4 or later which should contain proper input sanitization. Until patched, avoid clicking untrusted links to the affected site.

Recommended fix High confidence

Grand Conference theme version 2.6.4

  1. Create a complete backup of the WordPress site including database and files
  2. Navigate to WordPress Admin > Appearance > Themes
  3. Deactivate the current Grand Conference theme (or switch to a default theme temporarily)
  4. Delete the current Grand Conference theme installation
  5. Download Grand Conference theme version 2.6.4 or later from ThemeGoods (the official vendor)
  6. Upload and install the new version through WordPress Admin > Appearance > Add New > Upload Theme
  7. Activate the newly installed Grand Conference theme
  8. Verify the theme version is now 2.6.4 or later in Appearance > Themes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Grand Conference Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64224 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data