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

CVE-2025-68983

HIGH · 7.5 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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.11.

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 the thembay Greenmart WordPress theme. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file path parameters to include arbitrary local PHP files. This can lead to sensitive file disclosure or remote code execution depending on server configuration.

MitigationUpdate the Greenmart theme to the latest version as soon as a patch is released. As an interim measure, validate and sanitize all file inclusion parameters, disable allow_url_include in PHP configuration, and implement whitelisting for allowed include paths.

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

CVSS:3.1/AV:N/AC:H/PR:L/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 Greenmart theme is installed
    Navigate to wp-content/themes/ or check through WordPress admin Appearance > Themes to verify the Greenmart theme is present and active
    Affected if The Greenmart theme by thembay is installed and active in the WordPress environment
  2. Identify installed theme version
    Check the style.css file in the theme directory (wp-content/themes/tbay-greenmart/) for the 'Version:' header, or look in the theme's functions.php file
    Affected if The version cannot be determined or is within an unpatched version range
  3. Check PHP allow_url_include setting
    Create a PHP info file (<?php phpinfo(); ?)) or run 'php -i' from command line to verify the allow_url_include directive in php.ini
    Affected if allow_url_include is enabled (value is On) - this increases LFI severity but the core vulnerability exists regardless
  4. Review web server logs for suspicious include/require requests
    Examine access logs for patterns like '?file=', '?path=', or '?template=' with directory traversal sequences (../) targeting PHP files in the theme directory
    Affected if Unexplained requests with ../ sequences or direct PHP file paths in query parameters are found

You are affected if the Greenmart theme is installed and running an unpatched version, regardless of PHP configuration - update immediately when a patch is released.

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

Update the Greenmart theme to the latest version as soon as a patch is released. As an interim measure, validate and sanitize all file inclusion parameters, disable allow_url_include in PHP configuration, and implement whitelisting for allowed include paths.

Recommended fix Moderate confidence

Greenmart theme version > 4.2.11 (latest available version)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to your WordPress dashboard > Appearance > Themes
  3. 3. Locate the Greenmart theme and check the current version number
  4. 4. If running version 4.2.11 or lower, update to the latest available version of Greenmart
  5. 5. If automatic updates are enabled, verify the theme has updated to the latest version
  6. 6. Test critical functionality (product pages, cart, checkout) to ensure the update did not break site operations
  7. 7. Verify the vulnerability is no longer exploitable by confirming the LFI vector is patched
Caveat Theme updates may require compatibility checks with your WooCommerce version and other plugins; test in staging first

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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