CVE-2025-28991
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in snstheme Evon snsevon allows PHP Local File Inclusion.This issue affects Evon: from n/a through <= 3.4.
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 confidenceA Local File Inclusion (LFI) vulnerability in snstheme Evon (snsevon) up to version 3.4 allows attackers to manipulate file inclusion functions (include/require) in PHP to read arbitrary local files from the server. This occurs due to improper control of filenames, likely without sanitizing user-supplied input used in file paths.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate snstheme Evon installationSearch for files or directories named 'snsevon', 'evon', or 'sns-theme' in the web root, typically under /wp-content/themes/ for WordPress or the application's template/partials directoryAffected if The snstheme Evon theme/plugin is present on the server
-
Identify the installed versionOpen the main PHP file (often named version.php, info.php, or the theme's main index.php) and locate the version definition variable or constantAffected if The version is 3.4 or lower, or no version is defined but the theme appears to be snsevon
-
Find file inclusion code using user inputSearch PHP source files for include, require, include_once, or require_once statements where the path contains variables that could originate from user input (e.g., $_GET, $_POST, $_REQUEST)Affected if File inclusion functions receive unsanitized user-controlled parameters without validation like basename() or whitelist filtering
-
Verify the vulnerable parameter is accessibleTest the identified file inclusion parameters via HTTP requests (GET/POST) using directory traversal sequences such as ../../../../etc/passwdAffected if The application returns the contents of arbitrary local files when traversal sequences are provided in the parameter
If snstheme Evon version 3.4 or lower is installed and contains file inclusion code using unsanitized user input, the environment is affected by CVE-2025-28991.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and whitelist-based filtering on all file inclusion parameters. Use basename() to strip directory traversal sequences (../), define allowed files explicitly, and avoid passing user input directly to include/require statements.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28991 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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