CVE-2023-35925 is a medium-severity (CVSS 6.2) Uncontrolled Resource Consumption vulnerability in com.fastasyncworldedit:FastAsyncWorldEdit-Core. A fix is available for com.fastasyncworldedit:FastAsyncWorldEdit-Core — see the affected versions and patch details below.
FastAsyncWorldEdit vulnerable to Uncontrolled Resource Consumption
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-35925.
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.
How urgent is this, really
CVE-2023-35925 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.fastasyncworldedit:FastAsyncWorldEdit-Core☕com.fastasyncworldedit:FastAsyncWorldEdit-BukkitReal-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
Coordinated Disclosure Timeline
- 10.06.2023: Issue reported to IntellectualSites
- 11.06.2023: Issue is acknowledged
- 12.06.2023: Issue has been fixed
- 22.06.2023: Advisory has been published
Impacted version range
Before 2.6.3
Details
Proof of Concept
As a user, do the following:
- Select position 1 via
//pos1 - Select position 2 adding the "Infinity" keyword via
//pos2 Infinity - Execute any further operation.
The steps 1 and 2 are interchangeable.
Impact
Such a task has a possibility of bringing the performing server down.
CVE
- CVE-2023-35925
Credit
This issue was discovered and reported by @SuperMonis.
Solution
On June 12, 2023, a patch, https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/2285, has been merged addressing the vulnerability. We strongly recommend users to update their version of FastAsyncWorldEdit to 2.6.3 as soon as possible.
Workarounds
There is no direct mitigation besides updating FastAsyncWorldEdit to a patched version.
Additional Information
Users with access to the logs/ folder or shell access on their server can try to identify possible abuses of this issue by going through the logs.
To sieve through the data, you can use the regex query \/\/pos[12] Infinity, then investigate all log entries that return results.
Disclosure Policy
If you discover a security vulnerability within our software, please report the issue according to our vulnerability disclosure policy.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.fastasyncworldedit:FastAsyncWorldEdit-Core | all versions | 2.6.3com.fastasyncworldedit:FastAsyncWorldEdit-Core:2.6.3 |
| ☕Maven | com.fastasyncworldedit:FastAsyncWorldEdit-Bukkit | all versions | 2.6.3com.fastasyncworldedit:FastAsyncWorldEdit-Bukkit:2.6.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.fastasyncworldedit:FastAsyncWorldEdit-Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.fastasyncworldedit:FastAsyncWorldEdit-Core to 2.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-35925 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-2023-35925 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-35925. 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-2023-35925 in your dependencies?
O3 Security finds CVE-2023-35925 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.