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

CVE-2025-31633

HIGH · 8.1 CVSS v3.1 Published 2025-05-23
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 Kiamo - Responsive Business Service WordPress Theme allows PHP Local File Inclusion. This issue affects Kiamo - Responsive Business Service WordPress Theme: from n/a through 1.3.3.

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 Kiamo WordPress theme (versions up to 1.3.3). The theme contains improper control of filenames in PHP include/require statements, allowing attackers to potentially include and execute arbitrary local PHP files on the server.

MitigationUpdate the Kiamo theme to the latest patched version if available. If no patch exists, replace the theme with a secure alternative or implement input validation with whitelist filtering on all include/require statements to prevent path traversal.

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. Confirm Kiamo theme is installed
    Check the WordPress themes directory (wp-content/themes/) for a folder named 'kiamo' or similar. List all installed themes and verify if Kiamo is present.
    Affected if The Kiamo theme folder exists in the WordPress themes directory.
  2. Identify installed Kiamo theme version
    Open the theme's style.css file (usually at wp-content/themes/kiamo/style.css) and look for the 'Version:' comment in the file header, or check for a version.php file within the theme folder.
    Affected if The reported version number is 1.3.3 or lower.
  3. Locate PHP include/require statements
    Search the theme's PHP files for include, include_once, require, or require_once statements. Examine those that concatenate or interpolate variables into the file path, particularly any that might receive input from $_GET, $_POST, or other user-supplied sources.
    Affected if The theme contains include/require statements using dynamic file paths derived from user input without sanitization.
  4. Check for path traversal in vulnerable code
    Inspect the identified include/require statements to see if they allow directory traversal (e.g., use of '../' or absolute paths in user-controlled parameters). Look for functions that directly pass request parameters into file paths.
    Affected if The code accepts user input in include/require statements without validating that the input is within an expected directory or whitelist.
  5. Verify web server access to vulnerable paths
    Confirm the web server process has read access to sensitive directories (such as /etc/passwd, configuration files, or other PHP files outside the theme) that could be targeted via the LFI.
    Affected if The web server user can read files outside the intended theme directory through the vulnerable include/require mechanism.

A system is affected if the Kiamo theme version is 1.3.3 or lower AND the theme contains dynamic include/require statements that accept unsanitized user input, allowing path traversal.

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

Update the Kiamo theme to the latest patched version if available. If no patch exists, replace the theme with a secure alternative or implement input validation with whitelist filtering on all include/require statements to prevent path traversal.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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