CVE-2025-64284
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 Majestic Support Majestic Support majestic-support allows PHP Local File Inclusion.This issue affects Majestic Support: from n/a through <= 1.0.7.
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 confidenceFile inclusion vulnerability in Majestic Support plugin allowing attackers to control filenames in PHP include/require statements. This enables remote code execution by including malicious PHP files, either locally or remotely, through unsanitized user input.
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.
-
Confirm Majestic Support plugin installationSearch for Majestic Support files in your web root or plugin directories. Look for directories or files named 'majestic-support', 'majestic_support', or similar patterns.Affected if The plugin files are present on the server.
-
Identify installed Majestic Support versionLocate the main plugin file (typically version.php, plugin.php, or similar) and read the defined version constant or variable. Compare against 1.0.7.Affected if The installed version is 1.0.7 or earlier.
-
Locate file inclusion code pathsSearch source code for PHP include, require, include_once, or require_once statements that use variables or parameters from user input without sanitization.Affected if Unsantized user-controlled input is used in include/require statements.
-
Inspect PHP configuration for remote inclusionCheck php.ini or use phpinfo() to verify the allow_url_include setting.Affected if allow_url_include is enabled (set to On).
-
Review input handling for file parametersExamine the code handling file inclusion parameters. Look for GET, POST, or COOKIE variables passed to include/require without validation through functions like basename(), realpath(), or allowlist checking.Affected if File inclusion parameters accept arbitrary paths or URLs without validation.
You are affected if Majestic Support plugin is installed with version 1.0.7 or earlier AND your code uses unsanitized user input in file inclusion operations.
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 dataUpgrade to a patched version of Majestic Support beyond 1.0.7. If no patch is available, implement strict input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64284 — 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-64284 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