VulnerabilityPublished 27 Oct 2025

CVE-2025-62783: Phoenix616 InventoryGui · Improper Enforcement of a Single, Unique Action

Affects Phoenix616 InventoryGuiSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium · fixed in 1.6.2 : update Phoenix616 InventoryGui when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.6.2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavencom.github.Phoenix616/InventoryGui`pkg:maven/com.github.Phoenix616/InventoryGui`Other threats	Affected =1.6.2-SNAPSHOT	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade the InventoryGui library to version 1.6.2-SNAPSHOT or later, where the vulnerability is fixed. Server administrators should audit their plugin dependencies to confirm the InventoryGui version in use. If immediate upgrading is not feasible, disabling the experimental Bundle item feature on the server will prevent exploitation of the vulnerability. Additionally, server operators should monitor plugin updates and maintain strict version control to avoid running vulnerable versions. Implementing server-side logging and anomaly detection to identify unusual item duplication patterns can help detect exploitation attempts. Finally, educating plugin developers about secure usage of GuiStorageElement and avoiding experimental features in production environments can reduce future risks.

Description

InventoryGui is a library for creating chest GUIs for Bukkit/Spigot plugins. Versions 1.6.1-SNAPSHOT and earlier contain a vulnerability where any plugin using the `GuiStorageElement can allow item duplication when the experimental Bundle item feature is enabled on the server. The vulnerability is resolved in version 1.6.2-SNAPSHOT.

Impact

For European organizations operating Minecraft servers, especially those hosting multiplayer environments or running Bukkit/Spigot plugins that depend on InventoryGui, this vulnerability poses a risk to the integrity of in-game assets. Item duplication can lead to economic imbalance within game servers, loss of player trust, and potential reputational damage for server operators. While it does not directly compromise sensitive data or server availability, the integrity breach could be exploited for cheating or fraud in competitive or commercial gaming environments. This may also indirectly affect organizations that rely on Minecraft servers for educational or promotional purposes. The impact is more pronounced for servers enabling the experimental Bundle item feature, which is not enabled by default, thus limiting exposure. However, servers that have enabled this feature to leverage new gameplay mechanics are at higher risk.

CWE-837Improper Enforcement of a Single, Unique Action (opens in a new tab)
Base weakness
The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction.
OWASP ASVS 4.0.3
V11.1.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 03:28 UTC

WeaknessesCWE-837

Technical details

References

Community reviews

Related threats