CVE-2026-28079
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 axiomthemes Conquerors conquerors allows PHP Local File Inclusion.This issue affects Conquerors: from n/a through <= 1.2.13.
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 confidenceLocal File Inclusion vulnerability in the Conquerors WordPress theme allows attackers to include arbitrary PHP files from the server filesystem through improperly validated file path parameters in include/require statements. This can lead to disclosure of sensitive files 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.
-
Confirm Conquerors theme is installedNavigate to wp-content/themes/ directory and check for a folder named 'conquerors' or 'conquerors-theme'. If using WordPress admin, go to Appearance > Themes to list installed themes.Affected if The Conquerors theme appears in the installed themes list.
-
Identify theme versionOpen the theme's style.css file (typically at wp-content/themes/conquerors/style.css) and locate the 'Version:' header in the CSS comment block at the top. Alternatively, check functions.php for a version constant.Affected if The version line is found and shows any version number.
-
Locate file inclusion functions in themeSearch the theme directory for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements. Use a command like 'grep -r "include(" wp-content/themes/conquerors/' or manually inspect common files like functions.php, header.php, and any file handling template requests.Affected if PHP files contain dynamic include/require statements that accept parameters.
-
Check for vulnerable parameter handlingExamine the include/require statements found in step 3. Look for cases where the included file path uses $_GET, $_POST, or $_REQUEST variables directly without sanitization, such as 'include($_GET["file"])' or 'require($theme_path . $_GET["path"])'.Affected if Any include/require statement uses raw user input (GET/POST parameters) to construct the file path.
-
Test for LFI accessibility (if identified)If vulnerable code is found, attempt a safe test by requesting a known benign file through the suspected parameter, e.g., '?file=../../../../wp-config.php' or similar path traversal pattern. Only do this in a non-production environment.Affected if The server returns content from files outside the intended theme directory.
The environment is affected if the Conquerors theme is installed and its PHP code contains include/require statements that use unsanitized user-supplied input to construct file paths.
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 path sanitization on all file inclusion operations; consider updating to patched version when available or disabling the vulnerable file inclusion functionality.
- 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-28079 — 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-28079 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