MinimogwpWordPress extension · Thememove
CVE-2025-60069
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 ThemeMove MinimogWP minimog allows PHP Local File Inclusion.This issue affects MinimogWP: from n/a through <= 3.9.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 confidenceA file inclusion vulnerability in ThemeMove MinimogWP theme allows attackers to control filenames used in PHP include/require statements, potentially enabling local file inclusion to read sensitive server files or remote file inclusion if allow_url_include is enabled. The vulnerability stems from improper validation of user-supplied input before passing it to include/require functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MinimogwpWordPress extension
<= 3.9.6CVSS 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 MinimogWP theme is installedCheck for the theme directory at /wp-content/themes/minimogwp/ or /wp-content/themes/minimog/ in your WordPress installation. List all installed themes in wp-content/themes/ and look for minimog-related folder names.Affected if The theme folder minimogwp or minimog exists in the themes directory.
-
Determine installed theme versionOpen the style.css file located in the MinimogWP theme folder and look for the 'Version:' declaration in the file header comment. Compare this version number against the affected range of <= 3.9.6.Affected if The version number found in style.css is 3.9.6 or lower.
-
Locate vulnerable include/require code patternsSearch within the MinimogWP theme folder for PHP files containing include, require, include_once, or require_once statements where variables are used for file paths without proper sanitization. Look for patterns like 'include($', 'require($', 'include($_', 'require($_' followed by file extensions.Affected if Any PHP file in the theme contains include/require statements using unsanitized variable parameters that could accept arbitrary file paths.
-
Check for exposed parameters that control file inclusionReview theme PHP files for GET, POST, or REQUEST parameters that feed into the include/require statements. Identify which endpoints or URL parameters could be manipulated by an attacker to inject path traversal sequences (such as ../../) or absolute paths.Affected if URL-accessible parameters exist that allow external control of file paths used in include/require statements.
You are affected if the MinimogWP theme is installed with version 3.9.6 or lower and contains PHP files with vulnerable include/require patterns that accept user-controlled file path 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 using whitelist approaches, apply basename() and realpath() to normalize file paths, and disable allow_url_include in php.ini to prevent remote file inclusion.
Fix this in Minimogwp
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60069 — 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-60069 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