CVE-2025-67615
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 bslthemes Myour myour allows PHP Local File Inclusion.This issue affects Myour: from n/a through <= 1.5.1.
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 Local File Inclusion (LFI) vulnerability in the bslthemes Myour theme allows attackers to manipulate include/require statements to execute arbitrary PHP files. This stems from improper validation of user-supplied input used in filename parameters, potentially enabling remote code execution if the attacker can upload or control included 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
- 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 Myour theme is installedCheck your WordPress themes directory for the 'myour' folder, typically at wp-content/themes/myour/Affected if The myour theme folder exists in your WordPress installation
-
Check Myour theme versionOpen the style.css file in wp-content/themes/myour/ and look for the 'Version:' header in the file commentsAffected if The version number found is lower than the fixed version (check theme developer's release notes for the patched version)
-
Identify vulnerable include/require patternsSearch PHP files in the theme for include(), require(), include_once(), or require_once() statements that use variables without sanitization - look for patterns like 'include($_GET[...])' or 'require($filename)' without validationAffected if Any include/require statements in theme PHP files accept raw user input without filtering or validation
-
Check for file upload functionalityReview theme PHP files for upload handlers, file management code, or functions that accept file input from usersAffected if The theme contains file upload or file handling features that could be combined with the LFI to execute uploaded PHP files
-
Verify web server file permissionsEnsure the web server user cannot write to directories accessible via the theme's include statements (particularly wp-content/uploads/ and theme directories)Affected if Uploaded or writable files exist in directories that could be included via the vulnerable code paths
You are affected if the Myour theme is installed AND contains vulnerable include/require patterns using unsanitized user input, especially if file upload capabilities exist that could be chained with this LFI for remote code execution.
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 dataUpdate Myour theme to the latest version once available, or implement input validation/allowlisting for all include/require statements to restrict which files can be included.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67615 — 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-67615 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