dbcve.org
Grand RestaurantWordPress extension · Themegoods

CVE-2025-39353

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-19
Fix available
A fix is available. Upgrade to after 7.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Restaurant grandrestaurant allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Grand Restaurant: from n/a through <= 7.0.

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

The Grand Restaurant WordPress theme by ThemeGoods (versions <= 7.0) contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This likely permits unauthorized access to administrative functions or sensitive data that should require proper authentication and session validation.

MitigationUpdate the Grand Restaurant theme to the latest version available from ThemeGoods to obtain the authorization fix. If the theme is no longer supported, implement server-level access controls or consider migrating to a supported theme alternative.

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 RestaurantWordPress extension
Affected:<= 7.0

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

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

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. Verify Grand Restaurant theme is installed
    Navigate to WordPress Admin > Appearance > Themes and check if the Grand Restaurant theme by ThemeGoods is active or installed.
    Affected if The Grand Restaurant theme by ThemeGoods is installed and active on the WordPress site.
  2. Check the installed theme version
    In WordPress Admin > Appearance > Themes, click on the Grand Restaurant theme details to view the version number. Alternatively, check the style.css file in the theme directory for the 'Version:' header.
    Affected if The displayed version is 7.0 or lower.
  3. Inspect theme security settings
    Access the WordPress admin dashboard and navigate to the theme options panel (typically under Grand Restaurant > Theme Options or Settings). Review any access control, permission, or security level settings configured within the theme.
    Affected if Security/authorization settings are configured with weak or missing access controls, or if the theme permits unauthenticated access to administrative features.
  4. Review user role capabilities
    In WordPress Admin > Users > Roles or using a role management plugin, examine what capabilities are assigned to subscriber, contributor, or non-authenticated users versus administrator roles.
    Affected if Lower-privileged users or unauthenticated users have access to administrative functions or sensitive data that should require higher privileges.

The site is affected if the Grand Restaurant theme version 7.0 or lower is installed and the missing authorization vulnerability allows access to functions that should require proper authentication and elevated privileges.

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.

From vendor data
Upgrade available Upgrade to a release after 7.0
Interim mitigation

Update the Grand Restaurant theme to the latest version available from ThemeGoods to obtain the authorization fix. If the theme is no longer supported, implement server-level access controls or consider migrating to a supported theme alternative.

Fix this in Grand Restaurant Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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