CVE-2025-29002
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 Simen snssimen allows PHP Local File Inclusion.This issue affects Simen: from n/a through <= 4.6.
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 confidenceThis is a Local File Inclusion (LFI) vulnerability in the Simen theme for snstheme. The vulnerability allows an attacker to include arbitrary local files from the server's filesystem through unsanitized input in PHP include/require statements, potentially leading to sensitive file disclosure or remote code execution.
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.
-
Identify Simen theme installationLocate the snstheme installation and identify if the Simen theme is present. Check for theme directory structures typically found in snstheme installations under /themes or /template directories.Affected if The Simen theme for snstheme is installed on the server.
-
Locate file inclusion PHP filesSearch the Simen theme directory for PHP files containing include, include_once, require, or require_once statements. Focus on files that handle routing or template loading.Affected if PHP files in the theme use include/require to load files based on user input.
-
Inspect input sources for file inclusionExamine the identified PHP files to determine which $_GET, $_POST, or other user-controllable parameters are used in include/require statements. Trace the data flow from input to the file inclusion function.Affected if User-controllable parameters (such as 'page', 'template', 'file', or similar) are directly used in include/require statements without sanitization.
-
Verify input validation presenceReview the code around file inclusion calls to check if basename(), realpath(), whitelist filtering, or other input validation functions are applied before the include/require statement executes.Affected if No input validation, sanitization, or whitelist filtering is applied to file inclusion parameters.
The environment is affected if the Simen theme for snstheme is installed and contains file inclusion code that uses unsanitized user input in PHP include/require statements.
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() and realpath() to validate that included files are within expected directories, and avoid user-controlled input in include/require statements.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29002 — 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-29002 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