EMQX up to 5.8.5 Novel Plugin unusual condition ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in EMQX up to 5.8.5. This affects an unknown function of the component Novel Plugin Handler. The manipulation leads to unusual condition. This vulnerability is traded as CVE-2025-52136. It is possible to initiate the attack remotely. There is no exploit available. The existence of this vulnerability is still disputed at present. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in EMQX up to 5.8.5. This issue affects some unknown functionality of the component Novel Plugin Handler. The manipulation with an unknown input leads to a unusual condition vulnerability. Using CWE to declare the problem leads to CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. Impacted is integrity. The summary by CVE is:
In EMQX before 5.8.6, administrators can install arbitrary novel plugins via the Dashboard web interface. NOTE: the Supplier's position is that this is the intended behavior; however, 5.8.6 adds a defense-in-depth feature in which a plugin's acceptability (for later Dashboard installation) is set by the "emqx ctl plugins allow" CLI command.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-52136 since 06/16/2025. The exploitation is known to be difficult. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 5.8.6 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-24070). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.0
CNA Vector (MITRE): 🔒
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: Unusual conditionCWE: CWE-754
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: EMQX 5.8.6
Timeline
06/16/2025 CVE reserved08/10/2025 Advisory disclosed
08/10/2025 VulDB entry created
08/10/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
Disputed: 🔍
CVE: CVE-2025-52136 (🔒)
GCVE (CVE): GCVE-0-2025-52136
GCVE (VulDB): GCVE-100-319349
EUVD: 🔒
Entry
Created: 08/10/2025 09:39Updated: 08/10/2025 19:44
Changes: 08/10/2025 09:39 (63), 08/10/2025 19:44 (1)
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.