CVE-2026-28007
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 ThemeREX Coinpress coinpress allows PHP Local File Inclusion.This issue affects Coinpress: from n/a through <= 1.0.14.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the ThemeREX Coinpress WordPress theme. Attackers can manipulate file inclusion parameters to include and execute arbitrary local PHP files, potentially leading to full server compromise through 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 Coinpress theme installationCheck your WordPress themes directory (wp-content/themes/) for the coinpress folder. Review theme style.css header for version number, or query via WordPress admin appearance section.Affected if The Coinpress theme by ThemeREX is present in the themes directory.
-
Retrieve theme version numberOpen wp-content/themes/coinpress/style.css and locate the 'Version:' declaration in the theme header comments. Alternatively, check theme functions.php for version constants.Affected if The reported version falls within a vulnerable range or cannot be determined (unknown/older version).
-
Locate file inclusion codeSearch theme PHP files for include(), include_once(), require(), or require_once() statements that use variables in the path (e.g., include($file), include($_GET['template'])). Check especially in template files and core theme files.Affected if File inclusion functions use unsanitized user-controlled input without validation or path traversal protection.
-
Inspect vulnerable parametersExamine the theme for parameters that accept file paths via GET/POST requests (common names: file, template, page, include, path). Test if these accept directory traversal sequences like ../Affected if Parameters accept path traversal sequences and load arbitrary local files from the server.
-
Review web server access logsCheck Apache/nginx access logs for repeated requests to theme files with unusual path parameters (e.g., ?file=../../wp-config.php). Look for 200 responses on non-theme PHP files.Affected if Logs show requests containing directory traversal patterns targeting the Coinpress theme.
You are affected if the Coinpress theme is installed, the version is unknown or within a vulnerable range, and file inclusion parameters accept unsanitized path input enabling directory traversal.
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 dataUpdate Coinpress theme to the latest version if a patch is available; otherwise disable or remove the theme. Implement strict input validation and path allowlisting on any file inclusion logic to prevent directory traversal.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28007 — 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-2026-28007 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