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

CVE-2025-67527

HIGH · 7.5 CVSS v3.1 Published 2025-12-09
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 trippleS Digiqole digiqole allows PHP Local File Inclusion.This issue affects Digiqole: from n/a through < 2.2.7.

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 · high confidence

A PHP Local File Inclusion (LFI) vulnerability exists in the Digiqole component where user-controlled input is used in include/require statements without proper validation, allowing attackers to include arbitrary local PHP files.

MitigationUpgrade to Digiqole version 2.2.7 or later. If immediate upgrade is not possible, implement input validation and path sanitization on file inclusion functions, and consider deploying a WAF as a temporary measure.

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. Locate the Digiqole installation directory
    Search for 'digiqole' folder in your web root, typically under wp-content/themes/ or wp-content/plugins/. Common paths: /wp-content/themes/digiqole/ or /wp-content/plugins/digiqole/.
    Affected if The Digiqole directory exists in your WordPress installation
  2. Check the installed Digiqole version
    Open the main style.css file in the Digiqole theme folder (usually wp-content/themes/digiqole/style.css) or a version.php/config.php file and look for a 'Version:' or similar version declaration. Compare this version number to 2.2.7.
    Affected if The installed version is lower than 2.2.7 (e.g., 2.2.6, 2.2.5, or any version below 2.2.7)
  3. Search for vulnerable include/require patterns
    Examine PHP files in the Digiqole directory for include(), require(), include_once(), or require_once() statements that use variables from $_GET, $_POST, or $_REQUEST without sanitization. Look for patterns like 'include($_GET["file"])' or 'require($theme_path . $_REQUEST["template"])'.
    Affected if Unsanitized file inclusion code using user input is found in any Digiqole PHP file
  4. Identify if the component is actively serving requests
    Check if the Digiqole theme is currently active or the plugin is enabled in WordPress admin. Visit your site's wp-admin > Appearance > Themes to confirm if Digiqole is the active theme.
    Affected if Digiqole is the active WordPress theme or the plugin is enabled
  5. Verify external attack surface
    Test if arbitrary file inclusion parameters are reachable by sending a test request to common Digiqole endpoints with a benign parameter (e.g., ?file=test.php). Check web server logs for suspicious include/require activity.
    Affected if User-controlled parameters are accepted and processed by Digiqole PHP files without validation

You are affected if Digiqole is installed with a version lower than 2.2.7 AND contains unsanitized file inclusion code using user input AND is currently active on your WordPress site.

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 Digiqole version 2.2.7 or later. If immediate upgrade is not possible, implement input validation and path sanitization on file inclusion functions, and consider deploying a WAF as a temporary measure.

Recommended fix Moderate confidence

Digiqole version 2.2.7 or later

  1. 1. Back up your current Digiqole installation and database before proceeding with any updates.
  2. 2. Download the latest version of Digiqole (version 2.2.7 or later) from the official trippleS/Digiqole source or repository.
  3. 3. Replace the existing Digiqole files with the new version, preserving your configuration and content files.
  4. 4. Verify that the new version is running by checking the admin panel or version information.
  5. 5. Test the application to ensure the file inclusion vulnerability has been remediated and normal functionality is intact.
Caveat Review release notes for version 2.2.7 to check for any feature changes or migration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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