CVE-2025-49297
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 · uneditedPath Traversal: '.../...//' vulnerability in Mikado-Themes Grill and Chow grillandchow allows PHP Local File Inclusion.This issue affects Grill and Chow: from n/a through <= 1.6.
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 confidenceA path traversal vulnerability exists in Mikado-Themes Grill and Chow (grillandchow) where the sequence '.../...//' can be used to navigate outside the intended directory and include arbitrary PHP files via local file inclusion. This critical LFI flaw can be exploited without authentication and may lead to remote code execution if an attacker can inject PHP code into accessible files.
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< 1.6.1CVSS 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 Grill And Chow theme installationLocate the theme files in your WordPress installation under wp-content/themes/ and check for a folder named 'grillandchow' or similar. Look for a style.css file inside that folder and check the 'Version:' header in the file comments.Affected if The theme folder exists and the version header shows a version lower than 1.6.1 (e.g., 1.6, 1.5, 1.0).
-
Find PHP files with file inclusion functionsSearch the theme directory for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements, particularly those using variables in the path (e.g., include($file) or require($_GET['file']).Affected if Files exist that use dynamic file inclusion with user-controlled input without proper sanitization.
-
Search for path traversal vulnerability patternExamine the identified file inclusion code for the pattern '../' or '.../...//' being used in file paths, and verify if there is missing realpath() or basename() validation on the input.Affected if The code accepts file paths without validating they stay within an allowed directory, allowing '.../...//' sequences to traverse upward.
-
Verify web-accessible file inclusion endpointCheck if any PHP file handling user input is accessible via the web (in wp-content/themes/grillandchow/ or subdirectories) and accepts a parameter that could be manipulated for file inclusion.Affected if An endpoint exists that can be reached via HTTP request and passes user input to a file inclusion function without validation.
-
Compare installed version to affected rangeIf version information is available, compare your installed version directly against the affected range: versions less than 1.6.1 are vulnerable.Affected if The installed version is any version below 1.6.1 and the vulnerable code path is present and accessible.
You are affected if the Grill And Chow theme version is below 1.6.1 AND the theme contains PHP code that performs file inclusion with unsanitized user input allowing the '.../...//' traversal pattern.
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.
dbcve · scoped1.6.1
Implement strict input validation using realpath() and basename() to ensure file paths cannot traverse beyond the allowed directory. Restrict or disable PHP file inclusion functions, disable allow_url_fopen/allow_url_include, and update to a patched theme version when available.
Grill and Chow theme version 1.6.1
- 1. Backup your current WordPress installation and database before making any changes.
- 2. Navigate to your WordPress admin dashboard.
- 3. Go to Appearance > Themes.
- 4. Locate the 'Grill and Chow' theme.
- 5. Check the current version of the theme (visible in the theme details panel).
- 6. If the version is below 1.6.1, check for a theme update from the theme developer (Mikado-Themes) or your theme provider.
- 7. Update the theme to version 1.6.1 or later.
- 8. Verify the update was successful by confirming the new version number.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49297 — 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-49297 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