Quick answers
- Is CVE-2022-51015 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-51015 being exploited in the wild.
- How severe is CVE-2022-51015?
- Medium severity, with a CVSS score of 6.5, published 7 September 2026.
- Which products and versions are affected?
- pocketmine/pocketmine-mp (Packagist) ECOSYSTEM:introduced=0,fixed=4.0.6.
- Is there a fix for CVE-2022-51015?
- Yes. pocketmine/pocketmine-mp (Packagist): upgrade to 4.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-51015 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-51015?
- Check whether you run pocketmine/pocketmine-mp (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pocketmine/pocketmine-mp (Packagist): upgrade to 4.0.6 or later
composer require pocketmine/pocketmine-mp:^4.0.6
Technical details
The vulnerability is an input validation failure in PocketMine-MP's packet handling code. Specifically, the server does not validate that "facing" values in PlayerActionPacket (for START_BREAK and CRACK_BLOCK actions) and UseItemTransactionData are within the valid range of 0–5. An authenticated, network-reachable attacker can send PlayerActionPacket or InventoryTransactionPacket with out-of-range or negative facing values to trigger an unhandled exception and crash the server process. The fix, implemented in version 4.0.6, adds explicit validation of facing values before processing these packets.
Affected products
- PocketMine PocketMine-MP before 4.0.6
Identifiers
- CVE-2022-51015
- GHSA-xh99-hw7h-wf63
Timeline
- 2022-01-13: disclosed
- 2022: patched: Fixed in version 4.0.6 via commit f126479c37ff00a717a828f5271cf8e821d12d6c