CVE-2026-27988
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 Equadio equadio allows PHP Local File Inclusion.This issue affects Equadio: from n/a through <= 1.1.3.
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 confidenceThemeREX Equadio plugin <= 1.1.3 contains a PHP Local File Inclusion (LFI) vulnerability where improper control of filenames in include/require statements allows attackers to include arbitrary PHP files from the server file system, potentially leading to 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.
-
Locate ThemeREX Equadio plugin installationCheck your WordPress or website file system for the /wp-content/plugins/equadio or /plugins/equadio directory, or search for files containing 'equadio' in the name.Affected if The plugin directory exists on the server.
-
Determine installed plugin versionOpen the main plugin PHP file (typically equadio.php or index.php inside the equadio folder) and look for a version comment, version constant, or plugin header that states the version number.Affected if The version displayed is 1.1.3 or lower.
-
Confirm WordPress admin plugin list versionIf this is a WordPress site, log into the admin panel and navigate to Plugins > Installed Plugins. Locate 'ThemeREX Equadio' and compare the listed version against the affected range.Affected if The version shown in the WordPress admin is 1.1.3 or lower.
-
Identify file inclusion parameter exposureExamine the plugin source code, specifically looking for include(), require(), include_once(), or require_once() statements that use variables or request parameters (e.g., $_GET, $_POST) without proper sanitization in the file path.Affected if The plugin code contains unsanitized file inclusion that uses external input to construct file paths.
-
Test parameter accessibility (if identified)If a vulnerable parameter was found in the code review, attempt a benign LFI test using a known safe file path (e.g., ../../wp-config.php or ../../../../etc/passwd) via the identified GET/POST parameter, observing whether the file contents are returned.Affected if The parameter is accessible via HTTP request and successfully reads files outside the intended directory.
You are affected if the ThemeREX Equadio plugin is installed and its version is 1.1.3 or lower, and the vulnerable file inclusion parameter is accessible and exploitable on your server.
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 dataUpgrade to a patched version of Equadio. If no patch exists, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_fopen/allow_url_include in PHP configuration.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27988 — 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-27988 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