CVE-2025-62782 — inventorygui
Fix: Phoenix616/InventoryGui@00e684bCVE-2025-62782 is a CWE-837 vulnerability in de.themoep:inventorygui. A fix is available for de.themoep:inventorygui — see the affected versions and patch details below.
InventoryGUI vulnerable to item duplication via Bundle items when using GuiStorageElement
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-62782.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
de.themoep:inventoryguiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Any plugin using the GuiStorageElement is impacted when used on a server which allows the (currently experimental) Bundle items.
Patches
Patched with https://github.com/Phoenix616/InventoryGui/commit/00e684bd689ebc60bcb5b83ce4ef3c5a01778494 ("backported" to 1.6.3-SNAPSHOT)
Update to 1.6.4-SNAPSHOT to guarantee that it's included!
Workarounds
Don't enable the experiment "Bundle" items or don't use the GuiStorageElement in GUIs.
References
Original issue: https://github.com/Phoenix616/InventoryGui/issues/51
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | de.themoep:inventorygui | all versions | 1.6.4-SNAPSHOTde.themoep:inventorygui:1.6.4-SNAPSHOT |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.themoep:inventorygui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update de.themoep:inventorygui to 1.6.4-SNAPSHOT or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62782 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-62782 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-62782. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-62782 in your dependencies?
O3 Security finds CVE-2025-62782 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.