CVE-2025-63003
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 fuelthemes North - Required Plugin north-plugin allows PHP Local File Inclusion.This issue affects North - Required Plugin: from n/a through <= 1.4.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 · high confidencePHP Local File Inclusion vulnerability in fuelthemes North - Required Plugin (north-plugin) allows attackers to manipulate include/require statements to load arbitrary PHP files from the server file system, 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 North plugin is installedCheck your WordPress installation's wp-content/plugins or wp-content/themes/north directory, or use WP-CLI: wp plugin list --name=north-plugin or check theme version in style.cssAffected if The north-plugin theme or plugin is present in the WordPress installation
-
Determine installed plugin versionCheck the plugin header in north-plugin.php or the theme's style.css for the Version field, or query via WordPress admin plugins pageAffected if The version number is lower than the patched version or cannot be determined (assume vulnerable)
-
Inspect include/require usage in plugin codeSearch plugin files for dynamic include/require statements using variables: grep -r 'include\|require' --include='*.php' in the plugin directory, look for patterns like include($_GET['param']) or require($var)Affected if Dynamic file inclusion using user-controlled input is found without proper sanitization
-
Verify exposed input parametersTest any URL parameters used in include/require paths (e.g., ?file=../../etc/passwd or ?page=somefile) to see if they can manipulate file pathsAffected if The application allows path traversal or arbitrary file loading via URL parameters
-
Check PHP allow_url_include settingCheck php.ini for allow_url_include = On, or create a PHP info page: echo '<?php phpinfo(); ?>' > info.php and access itAffected if allow_url_include is enabled (makes LFI potentially more severe by allowing remote file inclusion)
You are affected if the North plugin/theme is installed and its version is lower than the patched version, or if dynamic file inclusion with unsanitized input is present in the code.
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 plugin to the latest patched version. If no update exists, implement strict input validation on all parameters used in include/require statements, use whitelist validation, and disable allow_url_include in PHP configuration.
- 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-63003 — 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-63003 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