CVE-2025-39379
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 Capturly Capturly capturly-optimize-your-website allows PHP Local File Inclusion.This issue affects Capturly: from n/a through <= 2.0.1.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Capturly capturly-optimize-your-website plugin (versions up to 2.0.1). The vulnerability allows attackers to manipulate file paths in include/require statements to read sensitive files on the server, potentially exposing configuration files, credentials, or source code.
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.
-
Confirm Capturly plugin is installedLocate the Capturly plugin files in the WordPress plugins directory (typically wp-content/plugins/capturly-optimize-your-website/). Check for the existence of this folder.Affected if The plugin folder exists in the WordPress installation.
-
Identify installed plugin versionOpen the main plugin PHP file (usually capturly-optimize-your-website.php or similar) and look for the version header comment or a version constant definition. Compare against the affected range (versions up to and including 2.0.1).Affected if The installed version is 2.0.1 or lower.
-
Locate vulnerable include/require statementsSearch plugin PHP files for dynamic include() or require() statements that use user-supplied input (e.g., $_GET, $_POST, or request parameters) as the file path without validation. Look for patterns like include($_GET['file']) or require($some_variable).Affected if Dynamic file inclusion code exists that uses unsanitized input parameters.
-
Verify the LFI trigger point is accessibleTest whether the vulnerable script endpoint is reachable via HTTP. Identify the specific PHP file handling the include/require and check if it accepts path parameters (e.g., ?file=../../../wp-config.php).Affected if The vulnerable script is directly accessible via web request and accepts file path parameters.
-
Check for sensitive file exposureAttempt to read a known local file (with authorization for testing only) via the suspected LFI parameter, such as a non-sensitive configuration file or a standard system file accessible to the web server user.Affected if The application returns contents of arbitrary files when path parameters are manipulated.
The environment is affected if the Capturly plugin versions up to 2.0.1 are installed and the vulnerable dynamic include/require code is accessible via a web request.
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 all file path parameters used in include/require statements, using allowlists to restrict access to permitted files only, or update to a patched version if available.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39379 — 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-39379 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