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

CVE-2025-49883

HIGH · 8.1 CVSS v3.1 Published 2025-06-27
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 Greenmart greenmart allows PHP Local File Inclusion.This issue affects Greenmart: from n/a through <= 4.2.3.

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

Greenmart theme <= 4.2.3 contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filenames in include/require statements allows attackers to read sensitive local files on the server via path traversal or by manipulating input parameters.

MitigationImplement strict input validation and whitelist-based filtering on any parameters used in include/require statements; use basename() to strip directory traversal sequences and avoid dynamic file inclusion where possible.

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 Greenmart theme installation and version
    Check the theme's style.css or version.php file typically found in wp-content/themes/greenmart/ for the version declaration
    Affected if The theme is installed and the version is 4.2.3 or lower
  2. Locate dynamic include/require statements
    Search the theme directory for PHP files containing include, require, include_once, or require_once statements that use variables in the file path (e.g., include($file), require($_GET['param'])
    Affected if Dynamic file inclusion using unvalidated variables is present in the theme code
  3. Identify user-controlled input reaching include/require
    Trace the variables used in include/require statements back to their source (GET, POST, REQUEST parameters) and verify if external input flows directly to the file path without validation
    Affected if User-supplied input from URL parameters or form data reaches the include/require statement without sanitization
  4. Check for path traversal protection
    Review the code handling the file path parameter for presence of basename(), realpath(), or allowlist validation before the include/require statement
    Affected if No path traversal protection (basename, realpath, or input validation) is implemented on the file parameter used in include/require
  5. Verify vulnerability is exploitable
    Test if the affected parameter accepts path traversal sequences (e.g., ../../../../etc/passwd) and returns file contents
    Affected if The parameter allows path traversal and returns contents of files outside the theme directory

A user is affected if Greenmart theme version 4.2.3 or lower is installed AND dynamic file inclusion with user-controlled input lacking path traversal protection exists in the theme 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

Implement strict input validation and whitelist-based filtering on any parameters used in include/require statements; use basename() to strip directory traversal sequences and avoid dynamic file inclusion where possible.

Recommended fix Moderate confidence

Latest available version of thembay Greenmart theme (version > 4.2.3)

  1. 1. Back up your WordPress site (database and files) before performing any updates.
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard.
  3. 3. Check if a newer version of the Greenmart theme is available. If the theme vendor has released a version newer than 4.2.3, update to the latest version.
  4. 4. If no update is available through the WordPress admin, manually download the latest version from the official thembay vendor source and upload/install it.
  5. 5. After updating, verify the vulnerability is remediated by reviewing any security patches mentioned in the theme changelog.
  6. 6. Consider implementing additional server-side protections: disable allow_url_include in php.ini, enable open_basedir restrictions, and review code for improper use of include/require with user input.
Caveat Review theme changelog for potential backward incompatibilities or required PHP version changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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