CVE-2025-68913
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 zozothemes Miion miion allows PHP Local File Inclusion.This issue affects Miion: from n/a through <= 1.2.7.
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 PHP Local File Inclusion (LFI) vulnerability in the zozothemes Miion theme (versions <= 1.2.7) allows attackers to include arbitrary local files via unsanitized input to include/require statements, potentially leading to 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Miion theme installationSearch for the 'miion' or 'Miion' directory in your web application's wp-content/themes/ folder or similar themes directory.Affected if The Miion theme directory exists in the themes folder.
-
Identify the installed versionOpen the theme's style.css file (typically at wp-content/themes/miion/style.css) and look for the 'Version:' comment in the file header. Compare this version number to 1.2.7.Affected if The version is 1.2.7 or lower.
-
Find include/require statements using dynamic inputSearch PHP files in the theme for patterns like 'include($_' or 'require($_' or 'include($' or 'require($' where a variable is passed directly to the include/require function without sanitization.Affected if The theme code contains include or require statements that use variable input without validation.
-
Check if URL parameters reach include/requireExamine the PHP files identified in step 3 to determine whether request parameters (e.g., $_GET, $_POST) can be passed to those include/require calls. Look for code that maps URL parameters to variables used in includes.Affected if User-supplied request parameters can flow to include/require statements without filtering.
-
Test for directory traversal capabilityIf dynamic includes exist, attempt to include a known local file using path traversal sequences (e.g., ../../) in the vulnerable parameter to confirm the LFI is exploitable.Affected if The include statement accepts and processes path traversal sequences, allowing arbitrary file inclusion.
You are affected if the Miion theme version is 1.2.7 or lower AND the theme contains include/require statements that accept unsanitized user input, allowing attackers to read or execute arbitrary local files.
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 Miion if available; otherwise, implement strict input validation and whitelist-based filtering on all include/require statements, and ensure directory traversal sequences are blocked.
- 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-2025-68913 — 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-68913 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