CVE-2025-69083
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 Elated-Themes Frappé frappe allows PHP Local File Inclusion.This issue affects Frappé: from n/a through <= 1.8.
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 Local File Inclusion (LFI) vulnerability in the frappe component of Elated-Themes allows attackers to manipulate file include/require statements to access sensitive local files via improper filename control in PHP code, rated high severity (CVSS 8.1).
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.
-
Locate the frappe componentSearch for directories or files named 'frappe' or containing 'frappe' in the web root or application directory. Common paths include /wp-content/themes/ or similar theme directories.Affected if The frappe component is found in the environment
-
Identify PHP files using include/requireIn the frappe directory, find all PHP files that contain 'include(', 'require(', 'include_once(', or 'require_once(' statements. Use grep or file search tools.Affected if PHP files with include/require statements exist in frappe
-
Check for dynamic file paths in inclusion statementsExamine the identified PHP files for include/require statements where the file path is built from variables, request parameters, or user input rather than hardcoded static strings. Look for patterns like include($var), include($_GET['file']), or include($path . $file).Affected if Dynamic or variable-based file paths are used in include/require statements without sanitization
-
Inspect input validation on file inclusionReview the code around include/require statements to determine if path traversal protections (such as basename(), realpath(), or whitelist validation) are implemented. Check if user-supplied parameters are validated before being used in file inclusion.Affected if No input validation, sanitization, or whitelist checking is performed on file paths before inclusion
-
Test for LFI exploitation potentialIf dynamic file inclusion is found without validation, attempt to access known local files (e.g., ../../../../etc/passwd or ../../wp-config.php) through the suspected parameter to confirm exploitability. Note: perform this only in authorized test environments.Affected if File traversal sequences (../) are accepted and local files can be read through the inclusion mechanism
The environment is affected if the frappe component is present and contains PHP files using dynamic file inclusion without proper input validation or whitelist-based path checking.
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 dataAudit and sanitize all include/require statements to implement strict whitelist-based path validation or remove dynamic file inclusion entirely; upgrade to a patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69083 — 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-69083 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