dbcve.org
Crafty ControllerApplication · Craftycontrol

CVE-2025-14701

HIGH · 7.1 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 4.6.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
An input neutralization vulnerability in the Server MOTD component of Crafty Controller allows a remote, unauthenticated attacker to perform stored XSS via server MOTD modification.

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 confidence

A stored cross-site scripting (XSS) vulnerability exists in the Server MOTD (Message of the Day) component of Crafty Controller. An unauthenticated remote attacker can inject malicious JavaScript payloads into the MOTD field, which gets stored and executed in the browsers of users who view the MOTD, due to insufficient input neutralization.

MitigationImplement strict input validation and context-aware output encoding on the MOTD field to neutralize malicious scripts before storage and before display to users.

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
Crafty ControllerApplication
Affected:< 4.6.2

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Crafty Controller version
    Locate the installed Crafty Controller version through the web interface (typically in Settings or About section), or check the application files/package metadata for the version number
    Affected if The installed version is lower than 4.6.2 (e.g., 4.6.1, 4.6.0, earlier versions)
  2. Verify MOTD component is in use
    Access the Server MOTD configuration area in the Crafty Controller web interface, typically found under Server Settings or Dashboard MOTD settings
    Affected if The MOTD feature is enabled and configured for any game server managed by Crafty Controller
  3. Inspect stored MOTD content
    Examine the MOTD field value currently saved in the Crafty Controller database or configuration file where the MOTD is stored
    Affected if The stored MOTD contains unsanitized HTML, JavaScript tags, or script-like content (e.g., <script>, javascript:, onload, onerror attributes)
  4. Check MOTD display behavior
    View the MOTD as displayed in a web browser (through the Crafty Controller dashboard or public server page) and inspect the page source to see if the MOTD content is rendered as raw HTML/JavaScript
    Affected if The MOTD content renders and executes as HTML or JavaScript in the browser rather than being displayed as plain text or properly escaped

You are affected if running Crafty Controller version 4.6.1 or earlier AND the MOTD feature is accessible, with stored MOTD content that executes as code in browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.6.2 or later
Fixed in 4.6.2
Interim mitigation

Implement strict input validation and context-aware output encoding on the MOTD field to neutralize malicious scripts before storage and before display to users.

Recommended fix High confidence

4.6.2 or later

  1. 1. Back up your current Crafty Controller configuration and data before proceeding with any upgrade.
  2. 2. Download the latest version of Crafty Controller (4.6.2 or later) from the official source at gitlab.com.
  3. 3. Stop the currently running Crafty Controller service.
  4. 4. Install the updated Crafty Controller version (4.6.2 or later).
  5. 5. Verify that the Server MOTD component now properly sanitizes input to prevent XSS attacks.
  6. 6. Restart the Crafty Controller service and confirm normal operation.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crafty Controller Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14701 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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