CVE-2020-25802
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 · uneditedImproper Control of Dynamically-Managed Code Resources vulnerability in Crafter Studio of Crafter CMS allows authenticated developers to execute OS commands via Groovy scripting. This issue affects: Crafter Software Crafter CMS 3.0 versions prior to 3.0.27; 3.1 versions prior to 3.1.7.
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 confidenceAuthenticated developers with access to Crafter Studio can execute arbitrary OS commands through Groovy scripting due to improper control of dynamically-managed code resources. This is an authenticated command injection vulnerability in the Groovy scripting engine of Crafter CMS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0.0, < 3.0.27>= 3.1.0, < 3.1.7CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 Crafter Studio versionCheck the version file or startup logs. The version is typically found in the Studio war file manifest, in a version.properties file under the installation directory, or in the startup logs (crafter-studio.log). Common paths include $CRAFTER_HOME/crafter-studio/version.txt or check the WEB-INF/lib directory for crafter-studio-*.jar and parse the version from the filename.Affected if The installed version is >= 3.0.0 and < 3.0.27, OR >= 3.1.0 and < 3.1.7
-
Verify Crafter Studio is exposedCheck if Crafter Studio web interface is accessible over network. Review server configuration files (such as server.xml for Tomcat or Nginx/Apache config) and firewall rules to determine if port 8080 (default) or the configured Studio port is externally accessible.Affected if Crafter Studio is reachable from untrusted networks or the internet
-
Confirm developer accounts existReview user database or LDAP configuration to identify accounts with developer-level permissions in Crafter Studio. These are the accounts that could potentially exploit the Groovy scripting functionality.Affected if There are authenticated developer users configured in Crafter Studio
A user is affected if Crafter Studio version is 3.0.0-3.0.26 or 3.1.0-3.1.6, AND the Studio interface is accessible to authenticated developers who can use Groovy scripting.
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.
From vendor data3.0.273.1.7
Upgrade Crafter CMS to version 3.0.27 or 3.1.7 or later to obtain the patched code. Additionally, limit Crafter Studio access to only trusted developers and apply the principle of least privilege.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25802 — 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-2020-25802 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