Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-7721: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in beardev JoomSport – for Sports: Team & League, Football, Hockey & more

0
Critical
VulnerabilityCVE-2025-7721cvecve-2025-7721cwe-98
Published: Fri Oct 03 2025 (10/03/2025, 11:17:11 UTC)
Source: CVE Database V5
Vendor/Project: beardev
Product: JoomSport – for Sports: Team & League, Football, Hockey & more

Description

The JoomSport – for Sports: Team & League, Football, Hockey & more plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5.7.3 via the task parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

AI-Powered Analysis

AILast updated: 10/03/2025, 11:25:48 UTC

Technical Analysis

CVE-2025-7721 is a critical vulnerability classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Programs) affecting the WordPress plugin 'JoomSport – for Sports: Team & League, Football, Hockey & more' developed by beardev. This vulnerability exists in all versions up to and including 5.7.3 and allows unauthenticated attackers to exploit a Local File Inclusion (LFI) flaw via the 'task' parameter. By manipulating this parameter, attackers can include arbitrary PHP files on the server, leading to remote code execution (RCE). This occurs because the plugin fails to properly sanitize or validate the filename input used in PHP include or require statements. The attacker can upload malicious PHP files (if upload functionality is available elsewhere or via other vulnerabilities) and then execute them by including them through the vulnerable parameter. The impact includes bypassing access controls, unauthorized data disclosure, and full system compromise. The vulnerability has a CVSS v3.1 base score of 9.8, indicating critical severity, with attack vector Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H). No known exploits are currently reported in the wild, but the ease of exploitation and severity make it a high-risk threat. The vulnerability was reserved in July 2025 and published in October 2025. No patches or fixes are currently linked, suggesting that users must monitor for updates or apply mitigations proactively.

Potential Impact

For European organizations, this vulnerability poses a significant risk, especially for those using WordPress sites with the JoomSport plugin to manage sports-related content. The ability for unauthenticated attackers to execute arbitrary PHP code can lead to complete server takeover, data breaches involving sensitive user or organizational data, defacement of websites, and disruption of services. This can damage reputation, lead to regulatory non-compliance (e.g., GDPR violations due to data exposure), and cause financial losses. Sports organizations, fan communities, and media outlets relying on this plugin are particularly vulnerable. The critical nature of the flaw means attackers can operate remotely without any credentials or user interaction, increasing the likelihood of automated exploitation attempts. Given the widespread use of WordPress in Europe and the popularity of sports content, the threat surface is substantial. Additionally, compromised sites could be used as pivot points for further attacks within corporate networks or to distribute malware to visitors.

Mitigation Recommendations

1. Immediate mitigation involves disabling or uninstalling the vulnerable JoomSport plugin until a patch is released. 2. If disabling is not feasible, restrict access to the vulnerable parameter by implementing Web Application Firewall (WAF) rules that block requests containing suspicious 'task' parameter values or attempts to include files. 3. Harden file upload mechanisms on the server to prevent uploading of executable PHP files, including strict MIME type and extension checks, and storing uploads outside the web root. 4. Employ PHP configuration settings such as 'open_basedir' to restrict file inclusion to safe directories. 5. Monitor web server logs for unusual requests targeting the 'task' parameter or attempts to include files. 6. Keep WordPress core and all plugins updated and subscribe to vendor security advisories for timely patching. 7. Conduct regular security audits and penetration testing focusing on file inclusion and code execution vulnerabilities. 8. Implement least privilege principles for web server and PHP process permissions to limit the impact of any successful exploitation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-07-16T16:45:22.676Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68dfb275c3835a5fbe033bf7

Added to database: 10/3/2025, 11:24:37 AM

Last enriched: 10/3/2025, 11:25:48 AM

Last updated: 10/7/2025, 12:36:48 PM

Views: 32

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats