Grand RestaurantWordPress extension · Themegoods
CVE-2025-32926
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ThemeGoods Grand Restaurant grandrestaurant allows Path Traversal.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 confidenceA path traversal vulnerability in the ThemeGoods Grand Restaurant theme (versions up to 7.0) allows attackers to access files outside the web root directory by manipulating path inputs, potentially leading to unauthorized file read/write operations.
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
<= 7.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Grand Restaurant theme versionLocate the theme's style.css file in wp-content/themes/grandrestaurant/ and read the 'Version:' header, or check the theme version via WordPress admin dashboard under Appearance > ThemesAffected if The version listed is 7.0 or lower (e.g., 6.9, 6.8, etc.)
-
Confirm the theme is active on the siteCheck WordPress admin > Appearance > Themes to verify the Grand Restaurant theme is currently activatedAffected if The theme is active and the version is 7.0 or below
-
Determine if file handling features are in useReview the theme's settings in WordPress admin for any enabled file upload, import, or download functionality (such as custom font upload, demo import, or settings backup features)Affected if File upload or import features are enabled and the theme version is vulnerable
-
Inspect for custom file handling codeSearch the theme directory (particularly functions.php and any files in includes/ or admin/ folders) for code that processes file path parameters, such as functions using include(), require(), file_get_contents(), or similar with user-supplied pathsAffected if Custom file handling code exists that accepts path parameters without strict validation
A user is affected if the Grand Restaurant theme version is 7.0 or lower AND the theme is active with file handling features or custom path-processing code present on their WordPress site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the Grand Restaurant theme; implement strict input validation and canonicalization for all file path parameters to prevent directory traversal sequences.
Fix this in Grand Restaurant
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32926 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32926 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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