dbcve.org
Grand ConferenceWordPress extension · Themegoods

CVE-2025-60116

HIGH · 8.8 CVSS v3.1 Published 2025-09-26
Fix available
A fix is available. Upgrade to 2.6.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Missing Authorization vulnerability in ThemeGoods Grand Conference Theme Custom Post Type grandconference-custom-post allows Exploiting Incorrectly Configured Access Control Security Levels.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 · high confidence

The Grand Conference WordPress theme (versions before 2.6.4) contains a missing authorization vulnerability in its custom post type functionality (grandconference-custom-post). The vulnerability allows unauthenticated or unauthorized users to bypass access controls and interact with the theme's custom post types that should require proper authorization checks.

MitigationUpdate the Grand Conference theme to version 2.6.4 or later to obtain the patch for this missing authorization vulnerability.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the Grand Conference theme and identify its version
    Access your WordPress installation via FTP or file manager. Navigate to /wp-content/themes/grandconference/ and open the style.css file. Look for the 'Version:' field in the theme header comment block.
    Affected if The version listed is less than 2.6.4 (for example, 2.6.3, 2.5.0, etc.) or if no version is specified but the theme is present.
  2. Verify the custom post type is registered
    In the same theme folder, open functions.php and search for 'grandconference-custom-post' or 'register_post_type'. Look for any custom post type registration that matches the theme functionality.
    Affected if The code contains a register_post_type call with 'grandconference-custom-post' or a similar theme-specific custom post type without proper authorization checks.
  3. Check if the custom post type is publicly accessible
    Attempt to access the custom post type URL on your site (for example, visit yourdomain.com/grandconference-custom-post or any post under that type) while logged out of WordPress admin.
    Affected if You can view, create, modify, or delete posts belonging to this custom post type without being logged in or without proper user privileges.
  4. Inspect the CPT capability requirements
    Review the theme functions.php code where the custom post type is registered. Look for 'capability_type', 'capabilities', 'map_meta_cap', or 'public' arguments in the register_post_type array.
    Affected if The CPT is set to 'public' => true without corresponding 'capabilities' restrictions, or if 'map_meta_cap' is not properly configured to enforce authorization.

You are affected if the Grand Conference theme version is below 2.6.4 and the grandconference-custom-post custom post type is registered and accessible without authentication or proper authorization checks.

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 to obtain the patch for this missing authorization vulnerability.

Recommended fix Moderate confidence

Grand Conference theme version 2.6.4

  1. 1. Create a complete backup of the WordPress site (database and files) before making any changes
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. 3. Locate the Grand Conference theme in the installed themes
  4. 4. Update the theme to version 2.6.4 or later
  5. 5. If automatic update is not available, manually upload the updated theme zip file from the theme vendor
  6. 6. Verify the theme version has been updated to 2.6.4 or higher
  7. 7. Test that the custom post type functionality works correctly
  8. 8. Confirm the authorization controls are now properly enforced

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60116 — 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-60116 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