CVE-2025-68987
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 Edge-Themes Cinerama cinerama allows PHP Local File Inclusion.This issue affects Cinerama: from n/a through <= 2.9.
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 confidenceThe Edge-Themes Cinerama theme (version <= 2.9) contains a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is used in include/require statements without proper validation. An attacker can manipulate the filename parameter to read sensitive local files from the server filesystem, potentially exposing configuration files, credentials, or source code.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 Cinerama theme installation and versionLocate the theme's version file (typically version.php, theme.json, or style.css in the theme directory) and read the declared version number.Affected if The installed version is 2.9 or lower.
-
Locate file inclusion code in theme PHP filesSearch the theme's PHP files for include, include_once, require, or require_once statements that use variables (e.g., include($file), require($_GET['filename'])) without hardcoded paths.Affected if User-supplied parameters are used directly in include/require statements without validation.
-
Inspect input validation on file parametersExamine the code handling file inclusion requests to determine whether the filename parameter is sanitized, uses a whitelist, or strips directory traversal sequences (..).Affected if No input validation, whitelist, or path traversal filtering is present on the filename parameter.
-
Verify web-accessible file inclusion endpointConfirm that the vulnerable PHP file handling file inclusion is accessible via HTTP/HTTPS on the web server.Affected if The endpoint accepting user input for file inclusion is exposed on the web.
A system is affected if it runs Cinerama theme version 2.9 or lower and exposes an unprotected PHP file inclusion mechanism that uses user input in 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 sanitization on all parameters used in include/require statements. Use a whitelist approach for allowed files, strip directory traversal sequences (..), and ensure the base directory is explicitly restricted to prevent path traversal attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68987 — 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-68987 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