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

CVE-2026-32531

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
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 gavias Kunco kunco allows PHP Local File Inclusion.This issue affects Kunco: from n/a through < 1.4.5.

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 Local File Inclusion (LFI) vulnerability in the Gavias Kunco WordPress theme that allows attackers to include arbitrary PHP files from the server filesystem through improper control of filename parameters in include/require statements. This can lead to sensitive file disclosure and potentially remote code execution depending on server configuration.

MitigationUpgrade to Kunco version 1.4.5 or later which contains the patched code. Until patched, disable PHP's allow_url_include setting and implement strict input validation with whitelist-based filtering on any file inclusion parameters.

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 Gavias Kunco theme is installed
    Check the wp-content/themes/ directory for the 'kunco' or 'gavias_kunco' folder, or use WordPress admin to list installed themes
    Affected if The Kunco theme folder exists in the WordPress themes directory
  2. Determine the installed Kunco theme version
    Open the style.css file in the Kunco theme folder (wp-content/themes/kunco/style.css) and locate the 'Version:' header in the file comments
    Affected if The version number found is lower than 1.4.5 (e.g., 1.4.4, 1.4.3, 1.3.0, etc.)
  3. Search for vulnerable file inclusion patterns in theme code
    Use grep or a text search to look for include/require statements using variable parameters in theme PHP files, particularly in files within the kunco folder that handle template or file loading
    Affected if Code contains include/require statements that use $_GET, $_POST, or unvalidated variables directly in filename parameters without sanitization
  4. Test for the LFI vulnerability via HTTP request
    Send a request to common theme endpoint URLs (such as template files in the theme directory) with a manipulated 'file', 'template', or 'path' parameter pointing to a known file (e.g., ../../../../wp-config.php)
    Affected if The server returns the contents of the specified file in the response, indicating the parameter is not properly sanitized

A user is affected if the Gavias Kunco theme version is installed and is lower than 1.4.5, or if vulnerable include/require patterns exist 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

Upgrade to Kunco version 1.4.5 or later which contains the patched code. Until patched, disable PHP's allow_url_include setting and implement strict input validation with whitelist-based filtering on any file inclusion parameters.

Recommended fix Moderate confidence

1.4.5

  1. 1. Backup your current Kunco theme installation and database before making any changes.
  2. 2. Download the latest version of the Kunco theme (version 1.4.5 or later) from the official gavias source or your purchase channel.
  3. 3. Replace the existing kunco theme files with the new version, ensuring all core files are updated.
  4. 4. Verify the theme version in your WordPress/WooCommerce admin panel to confirm the upgrade was successful.
  5. 5. Test critical functionality on your site to ensure the theme operates correctly after the upgrade.
  6. 6. If custom modifications exist, review them for compatibility with the new version and reapply any necessary security fixes.
Caveat Review custom modifications and child theme compatibility after upgrading, as template changes in the new version may affect overrides

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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