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

CVE-2025-28990

HIGH · 8.1 CVSS v3.1 Published 2025-06-27
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 SNS Vicky snsvicky allows PHP Local File Inclusion.This issue affects SNS Vicky: from n/a through <= 3.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

The SNS Vicky WordPress theme contains a PHP Local File Inclusion (LFI) vulnerability. Attackers can manipulate parameters used in include/require statements to traverse directories and include malicious PHP files, potentially achieving remote code execution on the server.

MitigationImplement strict input validation using whitelist approaches for file paths, avoid user-supplied input in inclusion functions, and ensure allow_url_fopen and allow_url_include are disabled. Update to a patched version if available from the vendor.

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. Locate the SNS Vicky theme installation
    Check your WordPress installation's wp-content/themes/ directory for a folder named 'vicky' or 'sns-vicky'. Use command: ls wp-content/themes/ | grep -i vicky
    Affected if The theme folder exists in your WordPress themes directory
  2. Identify the installed version
    Open the style.css file inside the theme folder and look for the 'Version:' header comment, or check theme functions.php for version definitions
    Affected if The version is unknown, unpatched, or falls within any vulnerable version range
  3. Examine the theme for file inclusion functions with user input
    Search the theme's PHP files (especially in includes/ or template files) for patterns like include(), require(), or include_once() that use parameters like 'file', 'path', 'template', 'page', or 'slug' without proper sanitization. Use grep: grep -r "\$_GET\|\$_REQUEST" --include="*.php"
    Affected if Any PHP file contains include/require statements using unsanitized user-supplied input from GET/REQUEST parameters
  4. Check for vulnerable parameter handling in core theme files
    Inspect main theme files (index.php, functions.php, page.php, single.php) and any included files in an 'includes/' subfolder for code that directly passes $_GET or $_REQUEST variables to include/require statements. Look for patterns like 'include($_GET["file"])' or 'require($theme_path . $_REQUEST["template"])'
    Affected if Code directly uses user-supplied input from URL parameters in file inclusion functions without validation or sanitization
  5. Verify if the vulnerable endpoint is accessible
    Test if the theme responds to direct requests that could trigger the LFI, such as ?file=../../../../etc/passwd or ?page=../../../wp-config (note: only test against your own environment with authorization)
    Affected if The application allows directory traversal through URL parameters in theme-related requests

You are affected if the SNS Vicky theme is installed and contains file inclusion code that uses unsanitized user input from URL parameters in include/require statements.

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 paths, avoid user-supplied input in inclusion functions, and ensure allow_url_fopen and allow_url_include are disabled. Update to a patched version if available from the vendor.

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