CVE-2026-25379
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 jwsthemes StreamVid streamvid allows PHP Local File Inclusion.This issue affects StreamVid: from n/a through < 6.8.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 · moderate confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the jwsthemes StreamVid theme where improper validation of filenames in include/require statements allows attackers to manipulate file path parameters to include arbitrary local PHP files. Successful exploitation can lead to remote 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.
-
Identify StreamVid theme installationLocate the theme directory in your web application (commonly in wp-content/themes/streamvid or themes/streamvid). Check for theme configuration files like style.css or theme.json that contain the theme name.Affected if The StreamVid theme by jwsthemes is present in the web application.
-
Determine installed StreamVid versionOpen the theme's style.css file or theme.json and look for the Version: field in the header comments. Alternatively, check version.php if it exists in the theme root directory.Affected if The version is lower than 6.8.6 (e.g., 6.8.5, 6.8.0, or any version below 6.8.6).
-
Search for vulnerable include/require patternsGrep the theme source code for dynamic include/require statements that use variable parameters, such as: include($_GET[...]), require($_REQUEST[...]), include($file), require($path). Look in PHP files within the theme directory.Affected if Dynamic include or require statements that accept user input without sanitization are found in the theme files.
-
Check for unsafe parameter usage in include statementsReview PHP files that handle file loading (commonly in functions.php, header.php, or custom include files). Look for patterns where $_GET, $_POST, or $_REQUEST variables are passed directly to include/require without basename() or allowlist validation.Affected if File path parameters from user input are used directly in include/require without validation.
-
Inspect web server access logs for LFI attemptsReview web server access logs (Apache access.log, Nginx access.log) for suspicious request patterns containing ../, ..\, or absolute paths in query parameters that may indicate LFI probing.Affected if Logs show repeated requests with path traversal sequences or direct file path arguments targeting PHP files.
A user is affected if the StreamVid theme version is below 6.8.6 AND the theme contains dynamic include/require statements using unsanitized user input from request 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.
dbcve · scopedUpgrade to StreamVid version 6.8.6 or later. Alternatively, implement strict input validation using allowlists and basename() functions to sanitize all include/require parameters, and disable allow_url_include if not needed.
6.8.6
- 1. Back up your current StreamVid installation before making any changes.
- 2. Download StreamVid version 6.8.6 or later from the official jwsthemes source.
- 3. Replace the existing StreamVid installation files with the new version.
- 4. Verify that the update was successful by checking the version number in the admin panel.
- 5. Test the application to ensure the file inclusion vulnerability is no longer exploitable.
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-2026-25379 — 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-25379 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