CVE-2026-22379
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 Netmix netmix allows PHP Local File Inclusion.This issue affects Netmix: from n/a through <= 1.0.10.
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 confidenceLocal File Inclusion (LFI) vulnerability in AncoraThemes Netmix theme allows attackers to read sensitive local files on the server through improper control of filename parameters in PHP include/require statements. The vulnerability affects versions up to and including 1.0.10.
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.
-
Identify if Netmix theme is installedLocate the theme files in your web application directory, typically under wp-content/themes/netmix or themes/netmix, or check your CMS theme management panel for the active themeAffected if The Netmix theme by AncoraThemes is present in your environment
-
Determine the installed Netmix theme versionCheck the style.css file within the theme directory for the 'Version:' header, or look for a version.php/changelog file in the theme folderAffected if The version number cannot be verified as patched or is earlier than any patched version released for this CVE
-
Search for vulnerable file inclusion patternsReview PHP files in the theme directory for dynamic include/require statements using user-supplied parameters (e.g., include($_GET['file']), include($var), require($_REQUEST['template']))Affected if Any PHP file contains dynamic file inclusion using request parameters without strict whitelist validation
-
Verify allow_url_include PHP settingCheck your php.ini or run phpinfo() to verify the value of allow_url_include directiveAffected if allow_url_include is enabled (set to On) and the application processes include statements with user input
-
Inspect for unexpected files or code artifactsLook for newly created PHP files in the theme directory, uploads folder, or web root that were not deployed by your team; check access logs for suspicious file inclusion requestsAffected if Unexpected PHP files exist or logs show repeated include parameter manipulation attempts
Your environment is affected if the Netmix theme is installed and uses dynamic file inclusion with user-controlled input without whitelist validation.
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 Netmix if available, or implement strict input validation with whitelist-based filtering for all file inclusion paths; avoid using user-supplied input directly in include/require statements.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22379 — 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-22379 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