CVE-2026-22410
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 Mikado-Themes Dolcino dolcino allows PHP Local File Inclusion.This issue affects Dolcino: 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 confidenceMikado-Themes Dolcino theme (version <= 1.6) contains a PHP Local File Inclusion (LFI) vulnerability where the application improperly validates or sanitizes input passed to include/require statements, allowing attackers to potentially read sensitive files from the server filesystem or achieve code execution.
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.
-
Locate the Dolcino theme installation directorySearch for the dolcino theme folder in your web root - common paths include wp-content/themes/dolcino, themes/dolcino, or similar directory structures depending on your CMS installationAffected if The dolcino theme folder exists on the server
-
Identify the installed Dolcino versionOpen the theme's style.css file (typically found in the theme root directory) and locate the version declaration in the file header comment - compare the version number against the affected range (<= 1.6)Affected if The declared version is 1.6 or lower, or no version is specified but the theme appears to be an older release
-
Examine PHP files for include/require statements with dynamic parametersSearch the theme's PHP files for include, include_once, require, or require_once statements that use variable or $_GET/$_POST parameters in the file path (e.g., include($_GET['file']) or include($filename))Affected if Dynamic file inclusion using user-controlled parameters is found in the codebase
-
Verify the vulnerable parameter is accessible via HTTPTest whether the affected parameter (typically a 'file', 'page', 'template', or similar name in URL query strings) can be manipulated through HTTP requests to trigger the include/require statements identified in step 3Affected if The parameter can be passed via HTTP and influences the file inclusion behavior
-
Check for sensitive file exposureAttempt to include known local PHP files through the vulnerable parameter (e.g., ../wp-config.php, /etc/passwd) using a controlled HTTP request - observe whether file contents are returnedAffected if Arbitrary local files can be included and their contents disclosed through the parameter
You are affected if the Dolcino theme version is 1.6 or lower AND the vulnerable dynamic file inclusion code is present and accessible via HTTP parameters.
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 and whitelist-based filtering on all parameters used in include/require statements to prevent path traversal; validate that included files exist within allowed directories.
- 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-22410 — 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-22410 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