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

CVE-2025-28944

HIGH · 8.1 CVSS v3.1 Published 2025-06-09
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 snstheme Avaz snsavaz allows PHP Local File Inclusion.This issue affects Avaz: from n/a through <= 2.8.

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 PHP Local File Inclusion (LFI) vulnerability in the snstheme Avaz theme (snsavaz) version 2.8 and below. The vulnerability allows remote attackers to include arbitrary PHP files via improperly sanitized user input used in PHP include/require statements, potentially leading to remote code execution.

MitigationImplement strict input validation using whitelist approaches for file inclusion paths, avoid using user-supplied input directly in include/require statements, and ensure all file paths are validated against an allowed directory.

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 snsavaz theme installation
    Look for theme files in the webroot directories, typically under /wp-content/themes/snsavaz/ for WordPress or similar theme directories for other PHP platforms. Check for the presence of theme configuration files like style.css, functions.php, or theme-specific PHP files bearing the snsavaz name.
    Affected if The snsavaz theme directory exists on the server.
  2. Determine installed snsavaz version
    Open the theme's main style.css or version.php file and locate the version declaration. Common locations include the theme header comment in style.css or a defined VERSION constant in functions.php. Compare the version number to 2.8 or lower.
    Affected if The installed version is 2.8 or any version lower than 2.8.
  3. Identify file inclusion code in theme PHP files
    Search the snsavaz theme directory for PHP files containing include, include_once, require, or require_once statements. Focus on files that appear to handle routing, templates, or dynamic content loading. Look for patterns where variable parameters are passed to these inclusion functions.
    Affected if PHP files in the theme use include/require with variables that could be user-controlled.
  4. Inspect input handling for include parameters
    Examine the identified file inclusion code to determine if parameters used in include/require statements originate from $_GET, $_POST, $_REQUEST, or similar superglobals without proper sanitization or validation against an allowed directory whitelist.
    Affected if User-supplied input from URL parameters, form inputs, or cookies flows directly into include/require statements without validation.
  5. Verify lack of path validation controls
    Check if the code implements whitelist validation, basename(), realpath(), or directory confinement checks before performing file inclusions. Look for security measures that restrict included files to a specific allowed directory.
    Affected if No whitelist, path normalization, or directory restriction is present before including files.

A user is affected if the snsavaz theme version 2.8 or below is installed AND the theme contains PHP code that uses unvalidated user input in include/require statements, allowing arbitrary file inclusion.

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 input validation using whitelist approaches for file inclusion paths, avoid using user-supplied input directly in include/require statements, and ensure all file paths are validated against an allowed directory.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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