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

CVE-2025-49252

HIGH · 8.1 CVSS v3.1 Published 2025-06-17
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in thembay Besa besa allows PHP Local File Inclusion.This issue affects Besa: from n/a through <= 2.3.8.

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

The Besa WordPress theme <= 2.3.8 contains a Local File Inclusion (LFI) vulnerability where PHP include/require statements do not properly validate user-controlled input, allowing attackers to read sensitive local files or potentially achieve code execution through manipulated file paths.

MitigationUpgrade to the latest Besa theme version which contains patched input validation, or implement strict whitelist-based validation on all file inclusion parameters and disable allow_url_include in php.ini.

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. Locate Besa theme installation
    Check wp-content/themes/besa/ directory for the theme files. Common paths: /wp-content/themes/besa/ or /wp-content/themes/besa-theme/. Verify the theme folder exists.
    Affected if The Besa theme folder exists in the WordPress themes directory.
  2. Identify installed Besa theme version
    Open the theme's style.css file located at wp-content/themes/besa/style.css and look for the 'Version:' declaration in the file header. Alternatively, check theme.json for version field.
    Affected if The version listed is 2.3.8 or lower (any version <= 2.3.8).
  3. Search for vulnerable file inclusion patterns
    Within the Besa theme folder, search PHP files for include, include_once, require, or require_once statements that use variables without sanitization. Use grep or similar: grep -r 'include\s*($' wp-content/themes/besa/ --include='*.php'. Look for patterns like 'include($_GET[...])' or 'require($var)' without validation.
    Affected if PHP files in the theme contain include/require statements using unsanitized user input (e.g., $_GET, $_POST, $_REQUEST variables) as file paths.
  4. Identify exposed file inclusion parameters
    Review theme PHP files that handle template loading or file serving. Look for parameters like 'file', 'path', 'template', 'page', 'view', or 'slug' passed via GET/POST that are used in include/require. Test suspected endpoints by passing a benign path like '/etc/passwd' to see if content is returned.
    Affected if The theme exposes an HTTP parameter that controls a file include path without validation, and the parameter is accessible via URL or form input.
  5. Confirm LFI vulnerability exists
    Attempt to read a safe local file by passing its path through the suspected parameter (e.g., ?file=../../../../wp-config.php). If the file content is displayed or included in the response, the LFI vulnerability is confirmed.
    Affected if The application returns contents of local files when path traversal sequences are used in the file inclusion parameter.

You are affected if the Besa theme is installed with version 2.3.8 or lower AND your server exposes a file inclusion parameter that accepts unsanitized user input within the theme's PHP code.

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

Upgrade to the latest Besa theme version which contains patched input validation, or implement strict whitelist-based validation on all file inclusion parameters and disable allow_url_include in php.ini.

Recommended fix Moderate confidence

Besa theme version 2.3.9 or later

  1. 1. Identify the current version of the Besa theme installed on the WordPress site
  2. 2. If the current version is <= 2.3.8, download the latest version of the Besa theme from a trusted source (them Bay official repository or marketplace)
  3. 3. Backup the current theme files and database before performing the upgrade
  4. 4. Upload and install the latest version of the Besa theme via WordPress admin panel or via SFTP/FTP replacement
  5. 5. Clear any caching mechanisms (plugin caches, server-side caches) after the upgrade
  6. 6. Verify the new version is installed by checking the theme version in WordPress admin under Appearance > Themes
  7. 7. Test critical functionality to ensure the upgrade did not break existing features
Caveat Review theme changelog for any template or functionality changes that may require adjustments to child theme customizations

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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