ThemeREX EmojiNation Plugin up to 1.0.12 on WordPress filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ThemeREX EmojiNation Plugin up to 1.0.12 on WordPress. It has been classified as critical. Affected by this issue is some unknown functionality. Performing a manipulation results in filename control. This vulnerability was named CVE-2026-28029. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in ThemeREX EmojiNation Plugin up to 1.0.12 on WordPress. It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a filename control vulnerability. CWE is classifying the issue as CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Improper 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.
The weakness was presented by Tran Nguyen Bao Khanh. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-28029 since 02/25/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/06/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 8.1
ADP CISA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Filename controlCWE: CWE-98
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/25/2026 CVE reserved03/05/2026 Advisory disclosed
03/05/2026 VulDB entry created
03/06/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Tran Nguyen Bao Khanh
Status: Not defined
CVE: CVE-2026-28029 (🔒)
GCVE (CVE): GCVE-0-2026-28029
GCVE (VulDB): GCVE-100-349053
Entry
Created: 03/05/2026 08:12Updated: 03/06/2026 17:02
Changes: 03/05/2026 08:12 (54), 03/06/2026 17:02 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.