CVE-2026-28029
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 EmojiNation emojination allows PHP Local File Inclusion.This issue affects EmojiNation: from n/a through <= 1.0.12.
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 confidenceThe ThemeREX EmojiNation WordPress plugin (versions <= 1.0.12) contains a Local File Inclusion (LFI) vulnerability where the plugin improperly validates user-supplied input before using it in PHP include/require statements. This allows authenticated or unauthenticated attackers to read sensitive files from the server's filesystem, potentially exposing configuration files, credentials, or other sensitive data.
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.
-
Check if EmojiNation plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'EmojiNation' by ThemeREX. Alternatively, check the /wp-content/plugins/ directory for a folder named 'emojination' or similar.Affected if The plugin is present in the WordPress installation
-
Identify installed plugin versionIn WordPress admin, find the EmojiNation plugin in the plugin list and note the version number displayed below the plugin name. Alternatively, check the main plugin PHP file for a 'Version' header comment.Affected if The installed version is 1.0.12 or lower
-
Verify plugin is activeIn WordPress admin > Plugins, check if EmojiNation shows as 'Active'. LFI may be exploitable even without authentication when the plugin is active.Affected if The plugin is active and running on the site
-
Inspect HTTP access logs for suspicious patternsReview web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for requests containing '../' or absolute path patterns targeting the plugin's PHP files. Search for unusual include/require patterns.Affected if Directory traversal sequences or path injection attempts are found in logs targeting the plugin endpoints
-
Check if plugin handles user input in include/require statementsIf you have code access, examine the main plugin PHP files for include(), require(), or similar functions that use variables from $_GET, $_POST, or $_REQUEST without proper sanitization.Affected if The plugin code uses user-supplied input in file inclusion functions without validation
A WordPress site is affected if the ThemeREX EmojiNation plugin version 1.0.12 or lower is installed and active, particularly if the plugin exposes endpoints that accept user-controlled 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 dataUpdate the EmojiNation plugin to the latest version as soon as a patch is released. If no update is available, disable the plugin immediately and consider removing it entirely. Implement web application firewall rules to block directory traversal patterns (e.g., ../../) as a temporary mitigation.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28029 — 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-28029 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