CVE-2025-68065
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 LiquidThemes Hub Core allows PHP Local File Inclusion. This issue affects Hub Core: from n/a before 6.0.2.
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 confidenceA PHP Local File Inclusion vulnerability exists in LiquidThemes Hub Core due to improper control of filenames in include/require statements. Attackers can potentially manipulate file paths to include arbitrary PHP files from the server, leading to code execution or disclosure of sensitive 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
- 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 Hub Core installation and identify versionSearch for Hub Core PHP files (commonly in /wp-content/themes/hub/ or similar paths) and check for version information in header comments, version.php files, or config files.Affected if The installed version is earlier than 6.0.2 (no version found or version below 6.0.2).
-
Review include/require statements in Hub Core PHP filesSearch the Hub Core directory for PHP files containing include, require, include_once, or require_once statements. Focus on files in the /core/ or /includes/ subdirectories.Affected if The code contains dynamic include/require statements that accept variables or parameters without validation.
-
Trace user input to file inclusion functionsExamine the identified include/require statements to determine if any user-controllable parameters (GET, POST, REQUEST, COOKIE) are passed as file paths. Check for patterns like include($_GET['file']) or require($var).Affected if User-supplied input directly reaches include/require without sanitization or path traversal checks.
-
Verify path traversal protection existsInspect the code surrounding file inclusion calls for functions that normalize paths (realpath, basename) or validate that the file is within an allowed directory.Affected if No path validation is implemented before include/require calls that accept user input.
The environment is affected if Hub Core version is earlier than 6.0.2 AND dynamic file inclusion code exists that accepts user input without path 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.
dbcve · scopedUpgrade to Hub Core version 6.0.2 or later which contains the fix. As a workaround, audit all include/require statements to ensure user-supplied input is properly validated and path traversal is blocked.
6.0.2
- 1. Backup your current Hub Core installation before proceeding with any updates.
- 2. Upgrade Hub Core to version 6.0.2 or later to resolve the Local File Inclusion vulnerability.
- 3. Verify the upgrade was successful by checking the Hub Core version in your admin panel.
- 4. Test that normal site functionality works as expected after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68065 — 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-68065 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