Skip to main content
VulnerabilityPublished

CVE-2025-14700: Arcadia Technology Crafty Controller · Template Injection

Affects Arcadia Technology Crafty ControllerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
6.5% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubcrafty-controller/craftypkg:github/crafty-controller/craftyOther threatsAffected
  • =4.6.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Apply security patches from Arcadia Technology as soon as they become available to address the vulnerability directly.
  2. Until patches are released, restrict access to the Crafty Controller Webhook Template component to trusted administrators only, using network segmentation and strict access controls.
  3. Implement multi-factor authentication (MFA) to reduce the risk of credential compromise that could enable exploitation.
  4. Monitor logs and webhook template usage for unusual or unauthorized template expressions indicative of attempted exploitation.
  5. Conduct regular audits of user accounts and permissions within Crafty Controller to minimize the attack surface.
  6. Employ web application firewalls (WAFs) or intrusion detection/prevention systems (IDS/IPS) with rules tailored to detect SSTI patterns.
  7. Educate administrators about the risks of template injection vulnerabilities and best practices for secure template usage.
  8. Consider temporary disabling or limiting the webhook template functionality if feasible until a patch is applied.

Description

An input neutralization vulnerability in the Webhook Template component of Crafty Controller allows a remote, authenticated attacker to perform remote code execution via Server Side Template Injection.

References

Community reviews

Loading reviews…