CVE-2025-39399
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 Ashraful Sarkar Naiem License For Envato license-envato allows PHP Local File Inclusion.This issue affects License For Envato: from n/a through <= 1.0.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 confidenceThe license-envato plugin 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 local PHP 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 license-envato pluginSearch the webroot for directories or files named 'license-envato' or 'envato', or list installed plugins in the CMS if this is a WordPress/plugin environmentAffected if The plugin directory exists in the environment
-
Identify the plugin versionCheck for a version.php, readme.txt, or composer.json file within the license-envato plugin directory to determine the installed version numberAffected if The version cannot be determined or is unknown compared to any affected version range
-
Find PHP files handling file inclusionSearch the plugin directory for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements that use variables or user input in the file pathAffected if PHP files use dynamic file inclusion without proper sanitization
-
Check for accessible entry pointsExamine the plugin's PHP files to identify any script endpoints that accept user input (via GET, POST, or REQUEST) and pass it to include/require functionsAffected if User-controlled parameters are directly used in include/require statements without validation
-
Verify lack of input validationReview the code around include/require calls to confirm there is no basename(), realpath(), whitelist validation, or other input sanitization before file inclusionAffected if The code lacks input validation and allows path traversal patterns in the included file path
A user is affected if the license-envato plugin is installed and its PHP code directly includes files based on unsanitized user input, allowing arbitrary local file inclusion.
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 dataImplement strict input validation on file inclusion paths using whitelisting or basename()/realpath() functions to prevent directory traversal and unauthorized file inclusion.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39399 — 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-39399 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