CVE-2026-28041
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Grit grit allows PHP Local File Inclusion.This issue affects Grit: from n/a through <= 1.0.1.
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 AncoraThemes Grit theme (version <= 1.0.1) contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filenames used in include/require statements. An attacker can manipulate the file path parameter to include arbitrary PHP files from the local server, potentially executing malicious code or accessing sensitive configuration files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check Grit theme versionLocate the theme's style.css file (typically in /wp-content/themes/grit/) and inspect the theme header comment for the 'Version:' field. Alternatively, search functions.php for a version constant definition.Affected if The reported version is 1.0.1 or lower
-
Identify LFI-vulnerable include patternsSearch all PHP files within the theme directory for include/require statements that use unsanitized variables, particularly $_GET or $_POST parameters in the file path. Use grep or manually inspect files that handle file loading functionality.Affected if Any PHP file contains include/require statements that incorporate user-supplied input directly into the file path without validation (e.g., include($_GET['file']);)
-
Locate the exploitable parameter handlerIdentify PHP files that accept a file path parameter (commonly named 'file', 'path', 'page', 'template', or similar) and pass it to include/require. Examine the request handling logic in the theme.Affected if A parameter accepting file paths is processed and passed to an include/require function without using basename(), realpath(), or whitelist validation
-
Test for LFI via HTTP requestSend a crafted request with a benign file path (e.g., ?file=../../../../wp-config.php or ?file=../../../../../etc/passwd) to PHP files in the theme directory that accept file parameters. Observe if the file contents are returned.Affected if The server returns the contents of files outside the theme directory, confirming the LFI vulnerability is exploitable
You are affected if the Grit theme version is 1.0.1 or lower AND the theme contains PHP files with include/require statements that accept unsanitized file path parameters from user input.
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 strict input validation using whitelist-based approaches for file paths, employ basename() and realpath() functions to normalize and validate paths, and disable allow_url_include to prevent remote file inclusion.
- 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-2026-28041 — 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-2026-28041 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