CVE-2026-28010
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 Scientia scientia allows PHP Local File Inclusion.This issue affects Scientia: from n/a through <= 1.2.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 · high confidenceThemeREX Scientia WordPress theme contains a PHP Local File Inclusion (LFI) vulnerability allowing attackers to include arbitrary local files via unsanitized user input in include/require statements. This can enable reading sensitive system files, configuration files, and potentially achieve code execution if writable files can be injected.
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 if ThemeREX Scientia theme is installedNavigate to wp-content/themes/ directory and check for a folder named 'scientia' or 'themerex-scientia'. In WordPress admin, go to Appearance > Themes to list installed themes.Affected if The ThemeREX Scientia theme folder exists in the themes directory.
-
Locate the vulnerable file inclusion codeSearch within the theme folder for PHP files containing include(), require(), include_once(), or require_once() that use variables from $_GET, $_POST, or $_REQUEST without proper sanitization. Look for patterns like 'include($_REQUEST["..."]' or similar.Affected if A PHP file in the theme uses unsanitized user input in file inclusion functions.
-
Verify the vulnerable parameter is accessibleTest if the theme exposes any HTTP parameter that gets passed to include/require. Common patterns include '?file=', '?path=', '?template=', or '?page=' in URLs pointing to the theme.Affected if HTTP parameters controlled by the user can influence which files are included.
-
Check for directory traversal capabilityAttempt to access the suspected parameter with values like '../../../../etc/passwd' or '..\..\..\windows\system32\drivers\etc\hosts' to see if the application allows traversal outside the intended directory.Affected if The application accepts and processes directory traversal sequences in the file inclusion parameter.
A user is affected if the ThemeREX Scientia theme is installed and contains PHP code that uses unsanitized user-supplied input in include/require statements, allowing arbitrary file reads.
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 using whitelist approach for file paths, use basename() to strip directory traversal sequences, and avoid using user input directly in include/require statements. Alternatively, refactor to use a safe mapping between allowed values and file paths.
- 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-28010 — 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-28010 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