CVE-2025-49365
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 AncoraThemes Jack Well jack-well allows PHP Local File Inclusion.This issue affects Jack Well: from n/a through <= 1.0.14.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the AncoraThemes Jack Well WordPress theme (versions <= 1.0.14). The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file path parameters to include arbitrary PHP files from the local server, potentially leading to 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.
-
Verify Jack Well theme versionAccess the theme directory via FTP or file manager, open style.css in wp-content/themes/jack-well/ and locate the 'Version:' header in the file commentsAffected if The version number listed is 1.0.14 or lower
-
Confirm theme is activeLog into WordPress admin dashboard, go to Appearance > Themes and check if Jack Well theme is the currently active themeAffected if Jack Well theme is enabled as the active theme on the WordPress site
-
Identify vulnerable include/require patternsSearch theme PHP files for include, require, include_once, or require_once statements that use variables (such as $_GET, $_POST, or directly concatenated user input) without proper sanitization. Common patterns include: include($_GET['file']); or require($path . $_REQUEST['template']);Affected if Unsanitized file path variables are used in include/require statements within theme PHP files
-
Check for parameter exposureReview PHP files that handle template or file loading logic. Examine any parameters that accept file paths or template names (often named 'file', 'path', 'template', 'page', 'include', or similar) to see if they flow directly to include/require statementsAffected if File path parameters can be manipulated through URL GET/POST requests to point to arbitrary local PHP files
A user is affected if the Jack Well theme version is 1.0.14 or lower, the theme is active on the WordPress site, and vulnerable include/require code patterns that accept unsanitized user input exist in the theme files.
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 the Jack Well theme to the latest patched version when available. Until then, disable the theme, audit the codebase for vulnerable include/require statements, implement strict input validation on file path parameters, and restrict file access permissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49365 — 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-49365 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