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

CVE-2025-22712

HIGH · 8.1 CVSS v3.1 Published 2026-01-08
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 QantumThemes Typify typify allows PHP Local File Inclusion.This issue affects Typify: from n/a through <= 3.0.2.

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

Improper control of filename for include/require statements in QantumThemes Typify allows attackers to include arbitrary PHP files from the local system (Local File Inclusion), potentially leading to remote code execution. The vulnerability stems from insufficient validation of user-controlled input used in file path parameters for include/require functions.

MitigationUpgrade to a patched version of Typify. As immediate mitigation, disable allow_url_include in php.ini, implement strict whitelist-based input validation on all include/require parameters, and consider deploying a WAF to block malicious file inclusion requests.

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 if Typify theme is installed
    Check your WordPress installation under wp-content/themes/ for the 'typify' or 'Typify' folder. Check the style.css or theme.json file for the theme version metadata.
    Affected if The Typify theme folder exists in the themes directory.
  2. Determine installed version
    Read the version field from the theme's style.css header or theme.json file. Compare this version against any publicly available version information for Typify releases.
    Affected if You cannot determine a safe version or are running an unpatched version of Typify.
  3. Locate vulnerable include/require patterns
    Search theme PHP files for include(), require(), include_once(), or require_once() statements that use variables or parameters in the file path without proper validation. Look for patterns like 'include($_GET[...])' or 'require($filename)'.
    Affected if Any PHP file in the theme contains dynamic include/require statements using user-controlled input without sanitization.
  4. Identify user-input filename parameters
    Review PHP files that handle file path parameters (often named 'file', 'path', 'filename', 'page', 'template', or similar). Check if these parameters are used directly in include/require statements.
    Affected if User-supplied parameters are used in include/require statements without allowlist validation or path sanitization.
  5. Check PHP configuration
    Review php.ini or check PHP info (phpinfo()) for the allow_url_include setting. Verify if open_basedir restrictions are properly configured.
    Affected if allow_url_include is enabled (value is 1 or On) and no open_basedir restrictions are in place.

You are affected if the Typify theme is installed and its PHP code contains vulnerable include/require statements that use unsanitized user input for file paths.

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 a patched version of Typify. As immediate mitigation, disable allow_url_include in php.ini, implement strict whitelist-based input validation on all include/require parameters, and consider deploying a WAF to block malicious file inclusion requests.

Recommended fix Moderate confidence

latest available version (higher than 3.0.2)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Update the Typify plugin to the latest available version from the WordPress plugin repository or QantumThemes
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  4. 4. Test that the Typify plugin functionality works correctly after the update
  5. 5. If available, review the changelog to confirm the security fix for CVE-2025-22712 is included

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