cve.bz

CVE-2025-49388 kamleshyadav miraculous core plugin: Incorrect Privilege Assignment

9.8 criticalEPSS 6.6%Fix available

Critical (9.8) in kamleshyadav miraculous core plugin. EPSS 6.6% estimated probability of exploitation activity in the next 30 days.

On this page
Incorrect Privilege Assignment vulnerability in kamleshyadav Miraculous Core Plugin miraculouscore allows Privilege Escalation.This issue affects Miraculous Core Plugin: from n/a through <= 2.0.7.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
6.6% (unchanged from 6.6% a week ago; 6.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-08-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-266 Incorrect Privilege Assignment
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • kamleshyadav Miraculous Core Plugin: fixed in 2.0.8

Ask an AI about this CVE

Show the promptExplain CVE-2025-49388 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-49388?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-49388?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-49388 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • kamleshyadav:miraculous core plugin

Versions

From the CNA's record in the CVE List.

ProductAffected
kamleshyadav Miraculous Core Pluginthrough 2.0.7

Fixed in

ProductFixed in
kamleshyadav Miraculous Core Plugin2.0.8

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • Nxploited/CVE-2025-49388 Harbor Check: matches CVE 1 star, created
    Miraculous Core (kamleshyadav) ≤ 2.0.7 — Unauthenticated Privilege Escalation

References

Check your stackJSON