dbcve.org
BusinextWordPress extension · Thememove

CVE-2025-58967

HIGH · 8.1 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 2.4.4 or later.
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove Businext businext allows PHP Local File Inclusion.This issue affects Businext: from n/a through < 2.4.4.

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 confidence

PHP Local File Inclusion vulnerability in ThemeMove Businext theme allows attackers to include arbitrary local files via improper control of filename parameters in include/require statements. This can enable reading sensitive files from the server filesystem.

MitigationUpdate Businext theme to version 2.4.4 or later. If update unavailable, implement strict input validation on all include/require parameters and restrict filesystem access permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BusinextWordPress extension
Affected:< 2.4.4

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. Locate and identify Businext theme version
    Find the theme's version number in the theme's main style.css file header, or in a version.php/version.json file within the theme directory. The version is typically declared in a comment block at the top of style.css as 'Version: x.x.x'
    Affected if The installed version is lower than 2.4.4, or the version cannot be determined and the theme appears to be an older release
  2. Identify PHP files with dynamic include/require usage
    Search the theme's PHP files for 'include' and 'require' statements that use variables or parameters in the file path, such as include($_GET['file']) or include($some_variable). Use grep or a code search tool to find patterns like 'include($' or 'require($' or 'include($_' within the theme folder
    Affected if Dynamic include/require statements exist that could accept user-supplied filename parameters without sanitization
  3. Verify input reaches include/require paths
    Examine the identified dynamic include/require files to trace whether HTTP request parameters (GET, POST, COOKIE) flow into the file path without validation. Check if parameters like 'file', 'page', 'path', 'template', or 'theme' are used in include/require statements
    Affected if User-controllable input from HTTP requests is directly or indirectly used in include/require file paths without proper validation or sanitization
  4. Check for sensitive file access capability
    If dynamic includes exist, test whether the vulnerability can be triggered by requesting a URL with a parameter like '?file=../../../../etc/passwd' or similar path traversal sequences pointing to sensitive system files
    Affected if The application permits path traversal sequences in include/require parameters and allows reading files outside the web root

You are affected if the Businext theme version is below 2.4.4 AND dynamic include/require statements exist that accept user input without validation, allowing arbitrary file inclusion.

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.

dbcve · scoped
Upgrade available Upgrade to 2.4.4 or later
Fixed in 2.4.4
Interim mitigation

Update Businext theme to version 2.4.4 or later. If update unavailable, implement strict input validation on all include/require parameters and restrict filesystem access permissions.

Recommended fix Moderate confidence

Businext 2.4.4 or later

  1. 1. Back up your current Businext installation including all files and database
  2. 2. Download Businext version 2.4.4 or later from the official ThemeMove source
  3. 3. Replace the existing Businext files with the new version, preserving any custom configuration files if required
  4. 4. Verify that the application functions correctly after the upgrade
  5. 5. Test that the file inclusion vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Businext Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58967 — 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-58967 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