CVE-2025-27107
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIntegrated Scripting is a tool for creating scripts for handling complex operations in Integrated Dynamics. Minecraft users who use Integrated Scripting prior to versions 1.21.1-1.0.17, 1.21.4-1.0.9-254, 1.20.1-1.0.13, and 1.19.2-1.0.10 may be vulnerable to arbitrary code execution. By using Java reflection on a thrown exception object it's possible to escape the JavaScript sandbox for IntegratedScripting's Variable Cards, and leverage that to construct arbitrary Java classes and invoke arbitrary Java methods. This vulnerability allows for execution of arbitrary Java methods, and by extension arbitrary native code e.g. from `java.lang.Runtime.exec`, on the Minecraft server by any player with the ability to create and use an IntegratedScripting Variable Card. Versions 1.21.1-1.0.17, 1.21.4-1.0.9-254, 1.20.1-1.0.13, and 1.19.2-1.0.10 fix the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIntegrated Scripting, a Minecraft mod for creating scripts in Integrated Dynamics, contains a sandbox escape vulnerability in its Variable Cards feature. By exploiting Java reflection on thrown exception objects, attackers can escape the JavaScript sandbox and construct arbitrary Java classes, enabling execution of arbitrary native code via java.lang.Runtime.exec() on the Minecraft server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Integrated Scripting mod is installedExamine the server's mods folder for a JAR file containing 'integratedscripting', 'integrateddynamics', or similar related mod files. Check the server's modlist or mod loader output.Affected if The mod is present in the mods directory
-
Determine the installed version of Integrated Scripting or Integrated DynamicsOpen the mod JAR file's meta-inf or examine the mod's metadata file (often in META-INF/mods.toml or a modinfo JSON). Alternatively, check the server console or mod list at startup for the mod version.Affected if The version number is lower than 1.21.1-1.0.17, 1.21.4-1.0.9-254, 1.20.1-1.0.13, or 1.19.2-1.0.10, or cannot be determined to be at or above any of these patched versions
-
Verify if Variable Cards feature is enabledCheck the server's configuration files (usually in config/integrateddynamics or similar) for settings controlling Variable Cards or the Integrated Scripting JavaScript engine. Look for boolean flags enabling the Variable Card system.Affected if Variable Cards are enabled and functional in the server configuration
-
Determine if untrusted players can create Variable CardsReview the server's permissions system, role configurations, or any Integrated Dynamics-specific access controls to see which player groups can create or use Variable Cards with custom JavaScript. Check if guest or untrusted users have this capability.Affected if Players without administrative trust can create or use Variable Cards containing custom scripts
A server is affected if the Integrated Scripting mod is installed with a version lower than the patched releases AND Variable Cards are accessible to players who are not fully trusted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedServer operators should immediately update Integrated Scripting to version 1.21.1-1.0.17, 1.21.4-1.0.9-254, 1.20.1-1.0.13, or 1.19.2-1.0.10 (whichever is compatible with their Minecraft version) to patch this arbitrary code execution vulnerability.
Upgrade to Integrated Scripting version 1.0.10 (for MC 1.19.2), 1.0.13 (for MC 1.20.1), 1.0.17 (for MC 1.21.1), or 1.0.9-254 (for MC 1.21.4)
- 1. Identify the current version of Integrated Scripting mod installed on the Minecraft server
- 2. Determine which Minecraft/Modloader version is in use (1.19.2, 1.20.1, 1.21.1, or 1.21.4)
- 3. Download the corresponding fixed version: for 1.19.2 use 1.0.10, for 1.20.1 use 1.0.13, for 1.21.1 use 1.0.17, or for 1.21.4 use 1.0.9-254
- 4. Replace the old IntegratedScripting mod JAR file in the mods directory with the new fixed version
- 5. Restart the Minecraft server to load the updated mod
- 6. Verify the mod loads correctly and check for any errors in server logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27107 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data