PHP
CVE-2025-64284
HIGH
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
Improper 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.
AnalysisAI
Local file inclusion in Majestic Support WordPress plugin versions ≤1.0.7 allows authenticated attackers with low-level privileges to include arbitrary PHP files from the server filesystem via improper filename control in include/require statements. With CVSS 7.5 (High), the vulnerability requires high attack complexity but can lead to complete confidentiality, integrity, and availability compromise. EPSS score of 0.10% (28th percentile) suggests low probability of mass exploitation. No public exploit code identified and not present in CISA KEV at time of analysis, though Patchstack tracking indicates vendor awareness.
Technical ContextAI
This is a PHP Local File Inclusion (LFI) vulnerability arising from CWE-98 (Improper Control of Filename for Include/Require Statement). Despite the CVE description mentioning 'PHP Remote File Inclusion', the technical details and Patchstack reference confirm this as an LFI issue. The vulnerability occurs when the Majestic Support WordPress plugin fails to properly sanitize user-controlled input before passing it to PHP's include() or require() functions. Attackers can manipulate file path parameters to traverse the filesystem and include local files, potentially including configuration files containing credentials, log files with sensitive data, or specially-crafted files that execute arbitrary PHP code. The affected product is the Majestic Support plugin for WordPress, a customer support ticketing system. The high attack complexity (AC:H) suggests the vulnerability may require specific conditions such as particular file structures, writable directories, or chained exploitation techniques to achieve meaningful impact.
Affected ProductsAI
The vulnerability affects Majestic Support plugin for WordPress in all versions from earliest release through version 1.0.7 inclusive. Majestic Support is a customer support and ticketing system plugin for WordPress websites. According to the Patchstack database reference, the vulnerability was addressed in version 1.1.1, indicating all versions prior to and including 1.0.7 remain vulnerable. Organizations running WordPress sites with this plugin installed should verify their installed version immediately. The specific CPE or detailed version enumeration data was not provided in the vulnerability disclosure, but the version range is definitively established as ≤1.0.7 affected, ≥1.1.1 patched.
RemediationAI
Immediately upgrade Majestic Support plugin to version 1.1.1 or later, which addresses this local file inclusion vulnerability according to Patchstack's vulnerability database. WordPress administrators should navigate to the Plugins section of their WordPress admin dashboard, locate Majestic Support, and update to the latest available version. If immediate patching is not feasible, implement compensating controls including restricting plugin access to only fully-trusted administrator accounts, reviewing user permission levels to minimize accounts with low-privilege authenticated access, implementing web application firewall rules to detect path traversal patterns in requests to the plugin, and monitoring server logs for suspicious file access patterns. Complete vulnerability details and remediation guidance are available in the Patchstack database at https://patchstack.com/database/Wordpress/Plugin/majestic-support/vulnerability/wordpress-majestic-support-plugin-1-1-1-local-file-inclusion-vulnerability. Organizations should also audit whether sensitive files (configuration files, logs, upload directories) are accessible via the web server and implement appropriate filesystem permissions to limit damage potential from LFI attacks.
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
NetAlertX (formerly PiAlert) versions 23.01.14 through 24.x before 24.10.12 allow unauthenticated command injection thro
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Same weakness CWE-98 – PHP Remote File Inclusion
View allShare
External POC / Exploit Code
Leaving vuln.today