CVE-2025-64216
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 ThemeSphere SmartMag smart-mag allows PHP Local File Inclusion.This issue affects SmartMag: from n/a through <= 10.3.0.
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 vulnerability in the ThemeSphere SmartMag WordPress theme (versions through 10.3.0) allows attackers to include and execute arbitrary local PHP files by manipulating file path parameters in include/require statements. This can lead to sensitive data exposure or remote code execution if attackers can control the 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
- 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.
-
Confirm SmartMag theme is installedLocate the SmartMag theme directory in the WordPress installation under wp-content/themes/smartmag/ or similar theme folder names used by ThemeSphere.Affected if The SmartMag theme directory exists on the server.
-
Identify the installed SmartMag versionOpen the theme style.css file (typically at wp-content/themes/smartmag/style.css) and locate the 'Version:' header in the file comments. Compare this version number to the affected range (through 10.3.0).Affected if The installed version is 10.3.0 or lower, or if the version header is missing/unreadable but the theme is present.
-
Locate vulnerable include/require patternsSearch theme PHP files for include/require statements that incorporate user-controlled parameters without proper sanitization. Look for patterns like include($_GET['file']) or require($theme_path . $_POST['path']) within the theme directory.Affected if Any PHP files in the theme contain include/require statements that use request parameters (GET/POST) to construct file paths without validation.
-
Check for exploitation attempts in logsReview web server access logs (Apache/nginx error and access logs) for directory traversal patterns such as ../, ..\, or requests targeting sensitive local files (e.g., /etc/passwp-content, wp-config.php) via theme endpoints.
You are affected if the SmartMag theme is installed with a version at or below 10.3.0 AND the theme contains include/require logic that uses unsanitized user input to load local PHP 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 dataUpdate SmartMag theme to the latest patched version once available. As an interim measure, implement a Web Application Firewall rule to block directory traversal patterns in request parameters and disable the theme if no patch is available.
- 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-64216 — 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-64216 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