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

CVE-2025-68877

HIGH · 7.5 CVSS v3.1 Published 2025-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 cedcommerce CedCommerce Integration for Good Market ced-good-market-integration allows PHP Local File Inclusion.This issue affects CedCommerce Integration for Good Market: from n/a through <= 1.0.6.

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 CedCommerce Integration for Good Market WordPress plugin has a Local File Inclusion (LFI) vulnerability where user-supplied input is used in PHP include/require statements without proper sanitization, allowing attackers to include arbitrary PHP files from the local server filesystem.

MitigationImplement strict whitelist-based validation for any file paths used in include/require statements, avoiding direct use of user input in file inclusion operations.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 plugin installation
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'CedCommerce Integration for Good Market' or 'CedCommerce GoodMarket'. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to 'ced-good-market' or containing 'goodmarket' in the plugins folder.
    Affected if The plugin is installed and active on the WordPress site
  2. Locate the plugin version
    In the WordPress plugins list, click on the plugin name to view its details, or check the main plugin PHP file header for a 'Version' comment. You may also check the readme.txt file in the plugin directory for version information.
    Affected if The installed version matches or falls within any affected version range for this CVE (compare your version to the affected ranges if known)
  3. Identify LFI-vulnerable code patterns
    Examine PHP files in the plugin directory, specifically looking for include(), require(), include_once(), or require_once() statements where variable parameters might be used. Search for patterns like 'include($_GET[' or 'require($' in the plugin source code.
    Affected if The plugin contains include/require statements using unsanitized user input (e.g., $_GET, $_POST, or similar superglobals) in the file path
  4. Test for directory traversal in parameters
    If a parameter appears to control a file path, attempt a controlled test by passing a benign path such as '../' or a known safe file path (e.g., '../../../../etc/passwd' on Linux) via the suspected parameter in a GET or POST request, observing whether the application returns file contents.
    Affected if The application returns content from files outside the intended directory, indicating the LFI vulnerability is exploitable
  5. Check web server file access permissions
    Review the web server user permissions and file ownership on the server. Ensure the web server process cannot access sensitive system files (e.g., /etc/passwd, configuration files with credentials).
    Affected if The web server user has read access to sensitive system or configuration files that could be exfiltrated via LFI

The environment is affected if the CedCommerce Integration for Good Market plugin is installed, contains include/require statements using unsanitized user input, and the web server can be tricked into reading 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 whitelist-based validation for any file paths used in include/require statements, avoiding direct use of user input in file inclusion operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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