dbcve.org
Grand RestaurantWordPress extension · Themegoods

CVE-2025-67922

HIGH · 7.1 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to 7.0.9 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 Restaurant grandrestaurant allows Reflected XSS.This issue affects Grand Restaurant: from n/a through < 7.0.9.

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

Reflected XSS vulnerability in the ThemeGoods Grand Restaurant WordPress theme allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in web pages without proper output encoding.

MitigationUpdate Grand Restaurant theme to version 7.0.9 or later which contains the fix for the reflected XSS 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 RestaurantWordPress extension
Affected:< 7.0.9

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 Restaurant theme is installed
    Access WordPress admin dashboard > Appearance > Themes to confirm if the Grand Restaurant theme by Themegoods is active or installed.
    Affected if The Grand Restaurant theme is present in the WordPress installation.
  2. Locate theme version information
    In WordPress admin, go to Appearance > Themes and click on the Grand Restaurant theme card to view the theme details. The version number is displayed in the theme description area.
    Affected if The theme version displayed is below 7.0.9.
  3. Verify version via theme files (alternative method)
    Access the WordPress site via FTP or file manager, navigate to wp-content/themes/grandrestaurant, and open the style.css file. The version is defined in the CSS header comment as 'Version: x.x.x'.
    Affected if The Version field in style.css shows a version lower than 7.0.9.
  4. Confirm affected version range
    Compare your discovered version number against the affected range: any version from 1.0.0 up to but not including 7.0.9 is vulnerable.
    Affected if The installed version is less than 7.0.9.

If the Grand Restaurant theme is installed and its version is below 7.0.9, the environment is affected by this reflected XSS vulnerability.

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 7.0.9 or later
Fixed in 7.0.9
Interim mitigation

Update Grand Restaurant theme to version 7.0.9 or later which contains the fix for the reflected XSS vulnerability.

Recommended fix High confidence

Grand Restaurant theme version 7.0.9

  1. Create a complete backup of the WordPress site including files and database
  2. Download Grand Restaurant theme version 7.0.9 from ThemeGoods (the official vendor)
  3. Log in to WordPress admin dashboard
  4. Navigate to Appearance > Themes
  5. Deactivate the current Grand Restaurant theme or replace it with the new version
  6. Upload and activate Grand Restaurant version 7.0.9
  7. Verify the theme is running version 7.0.9 by checking the theme details
  8. Clear any caching plugins and server-side caches
Caveat As with any theme update, review custom CSS and child theme modifications after upgrading to ensure compatibility with version 7.0.9

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

Fix this in Grand Restaurant Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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