CVE-2025-67938
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 Mikado-Themes Biagiotti biagiotti allows PHP Local File Inclusion.This issue affects Biagiotti: from n/a through < 3.5.2.
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 confidenceThe Biagiotti WordPress theme before version 3.5.2 contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is used in include/require statements without proper validation, allowing attackers to include arbitrary PHP files from the server filesystem.
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.
-
Confirm Biagiotti theme is installedLocate the theme files in your WordPress or CMS installation directory under wp-content/themes/ or similar themes folder. Look for a folder named 'biagiotti' or 'Biagiotti' that contains theme files like style.css, functions.php, or theme.json.Affected if The Biagiotti theme folder exists in your themes directory
-
Identify the installed theme versionOpen the theme's main style.css file or theme.json file in the Biagiotti theme folder. Look for a 'Version:' declaration in the CSS header or a 'version' field in theme.json. Compare this version number to 3.5.2.Affected if The installed version is lower than 3.5.2 or the version cannot be determined (older than fixed release)
-
Locate file inclusion code patternsSearch the theme's PHP files (especially in include/ or includes/ subdirectories, and files like functions.php, header.php, footer.php) for include, require, include_once, or require_once statements that use variables in the file path, such as 'include($', 'require($', 'include $_GET', 'require $_POST', or similar dynamic path constructions.Affected if Dynamic file inclusion statements using request parameters are found in the theme code
-
Verify if inclusion parameters are user-controllableExamine any identified dynamic include/require statements. Check if the variables used in the file path come from $_GET, $_POST, $_REQUEST, or other user-controlled sources without proper sanitization or validation.Affected if File inclusion paths directly incorporate unsanitized user input from URL parameters or form data
-
Test for LFI exploitation potentialIf dynamic file inclusion is found, attempt to access a known local file through the suspected parameter (e.g., adding ?file=../../../../../../etc/passwd or similar path traversal to a request). Verify if the application attempts to include the specified file.Affected if The application returns content from local files when path traversal sequences are provided in the parameter
You are affected if the Biagiotti theme is installed with a version lower than 3.5.2 and the theme contains dynamic file inclusion code that accepts user-controlled input without validation.
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 Biagiotti theme version 3.5.2 or later. If immediate upgrade is not possible, audit the theme code for vulnerable include/require statements and implement strict input validation using whitelist approaches or basename() filtering.
Biagiotti theme version 3.5.2 or later
- 1. Backup the entire website database and files before making any changes.
- 2. Locate the Biagiotti theme files in the WordPress/wp-content/themes/biagiotti directory.
- 3. Download the latest version of the Biagiotti theme (version 3.5.2 or later) from the theme vendor or your theme provider portal.
- 4. Replace the existing theme files with the new version, or use the theme update mechanism if available through your WordPress admin panel.
- 5. Verify the theme version has been updated to 3.5.2 or later in the WordPress admin under Appearance > Themes.
- 6. Test critical website functionality to ensure the update did not break any custom features or integrations.
- 7. Review the website logs for any errors or suspicious activity after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67938 — 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-67938 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