Security readout for executives and security teams
Plain-English summary
crontab-ui through version 0.4.2 reportedly lets an unauthenticated network attacker import a malicious database that triggers operating-system command execution. A compromised instance could expose secrets, alter scheduled jobs, disrupt services, or enable broader host compromise. Risk is highest when the application or its import endpoint is reachable from untrusted networks.
Executive priority
Act immediately on reachable deployments: isolate the interface, restrict imports, and investigate for compromise. The potential business impact includes host takeover, credential theft, altered scheduled operations, and service disruption. Track vendor guidance because the supplied sources do not name a patched version or vendor-approved permanent fix.
Technical view
The POST /import endpoint reportedly accepts arbitrary .db files and replaces the application database without validation. A crafted value in the imported hook field can reach shell execution, producing OS command injection classified as CWE-78. The CVSS 3.1 score is 9.8: network-accessible, low complexity, no privileges, and no user interaction.
Likely exposure
Potentially exposed deployments are crontab-ui versions through 0.4.2 whose POST /import endpoint is reachable by untrusted users. Internet exposure materially increases urgency. The bundle does not establish default deployment settings, authentication controls outside this endpoint, installation prevalence, or a complete authoritative affected-version range beyond the stated description.
Exploitation context
The supplied record describes unauthenticated remote command execution, but it does not report observed exploitation, and the CVE is not listed as KEV in the bundle. No public exploit evidence is provided. Treat reachable instances as high-risk without representing exploitation as confirmed.
Researcher notes
The central trust-boundary failure is unauthenticated replacement of application state with an attacker-controlled database, followed by unsafe shell handling of the hook field. The bundle identifies crontab.js as relevant source material but does not provide a patch commit, release advisory, confirmed exploit activity, or authoritative deployment prevalence.
Mitigation direction
- Immediately restrict crontab-ui and POST /import access to trusted administrators and networks.
- Disable or block database imports until vendor guidance confirms a safe release or mitigation.
- Inventory deployments and prioritize isolation of internet-accessible instances.
- Check the project and CVE record for updated remediation guidance.
- Preserve relevant logs and database artifacts if compromise is suspected.
Validation and detection
- Identify deployed crontab-ui versions and compare them with the stated through-0.4.2 range.
- Verify whether POST /import is reachable without authentication from untrusted networks.
- Review import requests, unexpected database replacements, and suspicious hook-field changes.
- Inspect scheduled jobs and host activity for unexplained commands or modifications.
- After mitigation, confirm untrusted clients cannot reach or use the import endpoint.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-72589 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TuranSecVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineTuranSec
CVE Reserved
- Source timelineTuranSec
Public Disclosure
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ProductCVE reference, TuranSec · third-party-advisory
- Vulnerable FileCVE reference, TuranSec · technical-description
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.