CVE-2025-69410
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 Edge-Themes Belletrist belletrist allows PHP Local File Inclusion.This issue affects Belletrist: from n/a through <= 1.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 · moderate confidenceThe Belletrist WordPress theme by Edge-Themes contains a PHP Local File Inclusion (LFI) vulnerability caused by improper control of filenames in include/require statements. An attacker could potentially exploit this to read sensitive local files or, depending on server configuration, achieve remote 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
- 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 Belletrist theme is installedNavigate to wp-content/themes/ directory and check for a folder named 'belletrist' or 'Belletrist'. In WordPress admin, go to Appearance > Themes to see all installed themes.Affected if The belletrist theme folder exists in the themes directory.
-
Determine the installed theme versionOpen the style.css file inside the belletrist theme folder and look for the 'Version:' header in the file comments. Alternatively, check the theme's main functions.php file for a version constant.Affected if The installed version is not yet patched or is within the vulnerable version range.
-
Check if the vulnerable LFI parameter is accessibleExamine theme files (particularly PHP files in includes/ or template-parts/ directories) for include/require statements that use unsanitized user input (e.g., $_GET, $_POST, or $_REQUEST). Look for patterns like 'include($_GET["file"])' or 'require("includes/" . $_POST["template"])'.Affected if The theme contains include/require statements using unsanitized input from request parameters.
-
Verify the theme is activeIn WordPress admin, go to Appearance > Themes and check if Belletrist is the currently active theme. Also check wp_options table for 'template' and 'stylesheet' values matching 'belletrist'.Affected if Belletrist is the active theme on the WordPress site.
-
Test for directory traversal accessIf accessible, attempt a safe test request with a known benign file path (e.g., a parameter that might be used for includes with ../ patterns). Check server logs for any directory traversal attempts or unusual include/require activity.Affected if The application allows directory traversal patterns (../../) in include/require parameters.
A user is affected if the Belletrist theme by Edge-Themes is installed (especially if active) and contains PHP code that uses unsanitized request parameters in include/require statements, allowing LFI exploitation.
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 to a patched version of the Belletrist theme when available. As an interim measure, implement web application firewall rules to block directory traversal patterns (e.g., ../../) and restrict file access permissions on the server.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69410 — 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-69410 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