CVE-2025-26735
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 Candid themes Grip.This issue affects Grip: from n/a through 1.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 · moderate confidenceRemote File Inclusion vulnerability in Candid's Grip theme allows attackers to control filenames used in PHP include/require statements, potentially executing arbitrary PHP code by including malicious remote or local 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Locate the Grip theme installationSearch for the 'grip' theme directory in your web application's themes folder. Common paths include /wp-content/themes/grip, /themes/grip, or similar. Use 'find' command or file manager to locate.Affected if The Grip theme directory exists in your web application's theme locations.
-
Identify the installed Grip theme versionCheck for a version file within the Grip theme directory, commonly named 'style.css', 'package.json', 'theme.json', or a 'readme.txt'. Open the file and locate the 'Version:' header or version field.Affected if The version cannot be determined or matches known vulnerable versions of the Grip theme.
-
Examine PHP files for unsafe include/require usageSearch within the Grip theme folder for PHP files containing include, require, include_once, or require_once statements. Look for cases where user-controlled input (GET, POST, or request parameters) is used as the filename without sanitization. Use grep: grep -r 'include.*\$_' or grep -r 'require.*\$_' .Affected if PHP files in the theme use include/require with variables derived from request parameters without validation.
-
Verify the theme is actively loadedCheck your application's configuration or database to confirm the Grip theme is set as the active theme. For WordPress, check wp_options table for 'template' or 'stylesheet' values. For other CMS, consult the system's theme configuration.Affected if The Grip theme is enabled and actively rendering pages on your site.
Your environment is affected if the Grip theme is installed, actively in use, and contains PHP include/require statements that accept unsanitized user input for file paths.
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 dataUpgrade to a patched version of Grip theme; until then, disable the theme or implement web application firewall rules to block suspicious file inclusion attempts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26735 — 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-26735 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