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

CVE-2025-48171

HIGH · 8.1 CVSS v3.1 Published 2025-08-20
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 Cena Store cena allows PHP Local File Inclusion.This issue affects Cena Store: from n/a through <= 2.11.26.

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

This is a PHP Local File Inclusion (LFI) vulnerability in thembay Cena Store (versions up to 2.11.26). The application improperly validates user-supplied input used in include/require statements, allowing attackers to traverse the filesystem and include arbitrary local files. This can lead to exposure of sensitive configuration files, credentials, source code, or potentially remote code execution if writable files can be included.

MitigationImplement strict input validation using whitelist approaches or basename()/realpath() functions to sanitize file path parameters before use in include/require statements. Consider using a mapping array for allowed files rather than direct user input.

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. Confirm thembay Cena Store installation and version
    Search for PHP files containing 'Cena Store', 'themabay', or version strings like '2.11' in the web root. Check for version files, composer.json, or footer/header files that display the version.
    Affected if The installed version is 2.11.26 or any earlier version of thembay Cena Store.
  2. Locate PHP include/require statements using user input
    Search source code for patterns like 'include($_GET', 'require($_GET', 'include($_POST', 'require($_REQUEST' or similar where request parameters are used directly in include/require statements.
    Affected if The application uses $_GET, $_POST, or $_REQUEST parameters directly in include/require without sanitization.
  3. Identify the file path parameter name
    Examine the vulnerable include/require code found in step 2 to determine which GET/POST parameter controls the file inclusion (commonly named 'page', 'file', 'controller', 'view', or similar).
    Affected if A request parameter is used as all or part of the file path in include/require without validation.
  4. Test for directory traversal capability
    Attempt to access the identified endpoint with path traversal sequences like '../' or absolute paths in the parameter (e.g., ?param=../../etc/passwd). Monitor if the application returns file contents outside the intended directory.
    Affected if The application accepts and processes directory traversal sequences in the parameter, allowing arbitrary file inclusion.
  5. Check for input validation on file inclusion parameters
    Review the PHP code handling the include/require to see if it uses functions like basename(), realpath(), whitelist arrays, or path traversal filtering before using the parameter.
    Affected if No input validation exists, or the validation can be bypassed, allowing arbitrary file paths to be included.

You are affected if thembay Cena Store version 2.11.26 or earlier is installed and the application contains include/require statements that use unsanitized request parameters, allowing directory traversal to include arbitrary local files.

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

Implement strict input validation using whitelist approaches or basename()/realpath() functions to sanitize file path parameters before use in include/require statements. Consider using a mapping array for allowed files rather than direct user input.

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-48171 — 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-48171 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