Grand RestaurantWordPress extension · Themegoods
CVE-2025-39352
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 · uneditedMissing 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 confidenceThe Grand Restaurant theme <= 7.0 by ThemeGoods contains a Missing Authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This Broken Access Control (BAC) issue permits unauthorized access to sensitive functionality or data that should require proper authentication and authorization checks.
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
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Verify Grand Restaurant theme versionLocate the theme's style.css file in wp-content/themes/grandrestaurant/ and read the Version header to identify the installed version numberAffected if Version is 7.0 or lower, matching the vulnerable range
-
Inspect theme PHP files for authorization checksSearch theme PHP files for WordPress authorization functions including current_user_can(), wp_verify_nonce(), check_admin_referer(), and similar capability and nonce validation functions on sensitive operationsAffected if Sensitive theme functions and endpoints lack proper authorization checks (current_user_can, nonce validation)
-
Test unauthenticated access to theme functionalityAttempt to access theme-related admin pages, AJAX endpoints, or sensitive features using a non-authenticated session or a low-privilege user account to verify if access controls are enforcedAffected if Sensitive functionality is accessible without proper authentication or authorization
-
Review access control configurationCheck the theme settings and WordPress user role capabilities to determine if the theme exposes administrative or sensitive functions that should require elevated privilegesAffected if The theme exposes protected functionality to unauthorized users or lower-privileged accounts
User is affected if the installed theme version is 7.0 or lower AND sensitive functions lack proper WordPress capability checks and nonce validation, allowing unauthorized access.
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 dataImplement proper authorization verification (WordPress capability checks and nonce validation) on all sensitive endpoints and functions within the theme. Conduct a full access control audit to identify and remediate all unprotected paths.
Fix this in Grand Restaurant
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39352 — 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-39352 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