dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-9993

HIGH · 8.1 CVSS v3.1 Published 2025-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

The Bei Fen WordPress Backup Plugin up to version 1.4.2 is vulnerable to Local File Inclusion via the 'task' parameter. Authenticated attackers with Subscriber-level access can include and execute arbitrary .php files on the server, leading to code execution. This exploitation is limited to PHP 7.1 or older environments.

MitigationUpdate the plugin to the latest version immediately. Additionally, upgrade PHP to version 7.2 or higher if possible, as the LFI exploitation path is only effective on PHP 7.1 and older.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Bei Fen plugin installation and version
    Check the WordPress plugin directory for 'bei-fen' or 'beifen' folder, or use wp-cli: wp plugin list --name='*bei*' --format=table. Alternatively, inspect the plugin's main PHP file header for the 'Version' comment.
    Affected if The plugin is installed and its version is 1.4.2 or lower
  2. Verify PHP version on the server
    Run 'php -v' from command line, or create a PHP info page: <?php phpinfo(); ?>, or check via WordPress: wp shell -e 'echo PHP_VERSION;'
    Affected if PHP version is 7.1 or older (the vulnerability only affects these versions)
  3. Confirm WordPress user roles with Subscriber access or higher
    List users with roles: wp user list --role=subscriber --format=count. Also check for roles above Subscriber (contributor, author, editor, administrator).
    Affected if Any user account exists with Subscriber-level access or higher, as these roles can exploit the flaw
  4. Test access to the vulnerable 'task' parameter
    If the plugin exposes an admin AJAX or front-end endpoint, inspect the plugin's PHP source for 'task' parameter handling in $_GET or $_REQUEST. Craft a test request: https://your-site.com/wp-admin/admin-ajax.php?action=beifen_task&task=../../../../wp-config.php (note: actual endpoint varies by plugin code).
    Affected if The 'task' parameter is processed without proper validation, allowing path traversal
  5. Review plugin source for LFI vulnerability pattern
    Search plugin files for include/require statements using the 'task' parameter: grep -r 'task' plugins/bei-fen/ and examine if $_GET['task'] or $_REQUEST['task'] is used directly in include/require calls without sanitization.
    Affected if The code directly uses the 'task' parameter value in include/require statements without sanitization

The environment is affected if the Bei Fen plugin is installed at version 1.4.2 or lower, the server runs PHP 7.1 or older, and user accounts with Subscriber-level access or higher exist, allowing the LFI via the 'task' parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version immediately. Additionally, upgrade PHP to version 7.2 or higher if possible, as the LFI exploitation path is only effective on PHP 7.1 and older.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9993 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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