# CVE-2025-52136: Missing authorization in EMQX

> Administrators can install arbitrary plugins via the Dashboard, potentially leading to code execution, though the vendor considers this intended behavior.

- **Severity:** Low 3.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** GHSA-qh53-xj96-333x

## What is CVE-2025-52136?

CVE-2025-52136 is a low-severity missing authorization vulnerability in EMQX, published on 10 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2025-52136?


## How do I fix CVE-2025-52136?

No fix has been published for CVE-2025-52136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52136 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52136 exists.

Public exploit code:

- EMQX控制台不出网利用 (github_poc): https://github.com/f1r3K0/CVE-2025-52136

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52136 and fix it if it is affected.

What it is: CVE-2025-52136 is a low-severity missing authorization vulnerability in EMQX, published on 10 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52136 exists.

Affected product: EMQX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52136/ (Markdown: https://insights.sbomify.com/CVE-2025-52136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52136
- OSV: https://osv.dev/vulnerability/CVE-2025-52136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52136/
Summaries are generated and may contain mistakes; the official description above is the record.