Skip to main content
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-9993: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in d3rd4v1d Bei Fen – WordPress Backup Plugin

0
High
VulnerabilityCVE-2025-9993cvecve-2025-9993cwe-98
Published: Tue Sep 30 2025 (09/30/2025, 03:35:27 UTC)
Source: CVE Database V5
Vendor/Project: d3rd4v1d
Product: Bei Fen – WordPress Backup Plugin

Description

The Bei Fen – WordPress Backup Plugin plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.4.2 via the 'task'. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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. This only affects instances running PHP 7.1 or older.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 18:27:57 UTC

Technical Analysis

CVE-2025-9993 identifies a Local File Inclusion vulnerability in the Bei Fen – WordPress Backup Plugin for WordPress, affecting all versions up to and including 1.4.2 when running on PHP 7.1 or older. The vulnerability stems from improper control of the filename used in include or require statements, classified under CWE-98. Specifically, the plugin fails to properly validate or sanitize the 'task' parameter, allowing authenticated users with Subscriber-level privileges or higher to manipulate this parameter to include arbitrary PHP files on the server. This can lead to remote code execution by executing attacker-controlled PHP code, bypassing access controls, and potentially exposing sensitive information stored on the server. The exploit requires authentication but no user interaction beyond login, and the attack surface is limited to environments running outdated PHP versions. The CVSS v3.1 score of 8.1 reflects the high impact on confidentiality, integrity, and availability, though the attack complexity is high due to the need for authentication and specific PHP version constraints. No patches or exploits are currently publicly available, but the vulnerability is publicly disclosed and should be treated as critical for affected environments.

Potential Impact

The impact of CVE-2025-9993 is significant for organizations using the Bei Fen – WordPress Backup Plugin on PHP 7.1 or older. Successful exploitation allows attackers to execute arbitrary PHP code on the web server, which can lead to full system compromise, data theft, defacement, or pivoting to internal networks. Confidentiality is at risk due to potential unauthorized data access, integrity is compromised through code execution and modification, and availability can be affected by disruptive payloads. Since the vulnerability requires only Subscriber-level authentication, attackers can leverage compromised or weak user credentials to escalate privileges and execute code. This threat is particularly critical for organizations relying on WordPress for content management and backup, especially those that have not updated PHP or plugin versions. The lack of known exploits in the wild currently reduces immediate risk but does not diminish the potential for future targeted attacks.

Mitigation Recommendations

1. Upgrade PHP to version 7.2 or later, as the vulnerability only affects PHP 7.1 and older. 2. Update the Bei Fen – WordPress Backup Plugin to the latest version once a patch is released; monitor vendor communications for updates. 3. Implement strict input validation and sanitization on the 'task' parameter to prevent inclusion of arbitrary files. 4. Restrict file upload capabilities and enforce file type restrictions to prevent uploading malicious PHP files. 5. Limit user privileges by enforcing the principle of least privilege, ensuring that Subscriber-level accounts have minimal permissions and monitoring for suspicious account activity. 6. Employ Web Application Firewalls (WAFs) with rules to detect and block attempts to exploit LFI vulnerabilities. 7. Conduct regular security audits and vulnerability scans focusing on outdated PHP versions and vulnerable plugins. 8. Monitor logs for unusual include or require calls and unexpected PHP file executions. 9. Consider isolating WordPress instances in containerized or sandboxed environments to limit impact of potential exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-09-04T14:36:59.293Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68db52afa473ffe031e44809

Added to database: 9/30/2025, 3:46:55 AM

Last enriched: 2/26/2026, 6:27:57 PM

Last updated: 3/24/2026, 6:52:11 PM

Views: 163

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 require Pro Console access. Upgrade inside Console → Billing.

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

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses