CVE-2025-64195
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 ThimPress Eduma eduma allows PHP Local File Inclusion.This issue affects Eduma: from n/a through <= 5.7.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 Local File Inclusion (LFI) vulnerability exists in the ThimPress Eduma WordPress theme (versions <= 5.7.6) due to improper control of filename parameters in PHP include/require statements. An attacker could potentially include and execute arbitrary PHP files from the local filesystem, leading to 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
- 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.
-
Verify Eduma theme versionAccess WordPress admin dashboard, navigate to Appearance > Themes, locate Eduma theme, and check the version number displayed. Alternatively, inspect the style.css file in wp-content/themes/eduma/ and look for the 'Version:' header.Affected if The displayed version is 5.7.6 or lower.
-
Identify vulnerable include/require endpointsSearch theme source files for PHP include/require statements that use dynamic input parameters. Look for patterns like 'include($_GET[...])' or 'require($param...)' within theme PHP files, particularly in ajax or template handler files.Affected if Any PHP file contains include/require statements using unsanitized user input from $_GET, $_POST, or $_REQUEST parameters.
-
Test for directory traversalIf vulnerable parameters are identified, attempt a controlled test request using '../' patterns (e.g., ?file=../../wp-config.php) to see if the application allows traversing outside the intended directory. Only perform this on non-production systems.Affected if The application returns content from files outside the intended directory scope or displays file contents in the response.
You are affected if the Eduma theme version is 5.7.6 or lower and your installation contains PHP include/require code paths that accept and process unsanitized user-supplied filename 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 · scopedUpdate Eduma theme to the latest patched version. If immediate update is not feasible, implement strict input validation on all parameters used in include/require operations and consider deploying a WAF rule to block directory traversal patterns.
Eduma version > 5.7.6 (latest available version from ThimPress)
- Identify the current installed version of ThimPress Eduma theme
- Backup the entire WordPress site and database before making changes
- Update Eduma to the latest available version from the official ThimPress source or WordPress theme repository
- Verify the update was successful and the new version is greater than 5.7.6
- Test critical site functionality to ensure the update did not break existing features
- Check for any related security advisories or additional required updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64195 — 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-64195 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