Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.26.7 and earlier, the schedule router does not enforce organization/role checks. As a result, any authenticated user can create, update, run, or delete schedules belonging to other organizations if they know the scheduleId/serverId. Schedule types server and dokploy-server write and execute scripts on the host or remote servers, enabling RCE on the Dokploy host or a target server.
Security readout for executives and security teams
Plain-English summary
Dokploy deployments at 0.26.7 or earlier can let any logged-in user control schedules across organizations if they know internal IDs. Some schedule types can run scripts on the Dokploy host or remote servers, so this can become full command execution. The bundle does not show active exploitation.
Executive priority
Treat this as urgent for any internet-accessible, shared, or production Dokploy deployment. A regular authenticated user may be able to execute commands on infrastructure, creating confidentiality, integrity, and availability impact.
Technical view
The schedule router lacks organization and role authorization checks. An authenticated user with a scheduleId or serverId can create, update, run, or delete other organizations' schedules. The server and dokploy-server schedule types write and execute scripts, enabling host or target-server RCE. CVSS is 9.9 with low privilege required.
Likely exposure
Self-hosted Dokploy instances running 0.26.7 or earlier are exposed, especially multi-user or multi-organization environments. Exposure depends on authenticated account access and knowledge of scheduleId or serverId values.
Exploitation context
The source bundle reports no KEV listing and provides no cited evidence of active exploitation. The attack requires authentication, but no user interaction, and can cross organizational boundaries once relevant IDs are known.
Researcher notes
The bundle attributes the issue to missing authorization in the schedule router and command execution through schedule script handling. CPE data is absent, and the provided sources do not name a specific exploit in the wild. Confirm fixed-version details from Dokploy guidance before final remediation signoff.
Mitigation direction
Identify all Dokploy instances and confirm whether they run 0.26.7 or earlier.
Follow the Dokploy advisory and release guidance to move off affected versions.
Restrict Dokploy access to trusted users until remediation is complete.
Review and reduce permissions for users who can access scheduling features.
Audit existing server and dokploy-server schedules for unexpected scripts or changes.
Validation and detection
Inventory Dokploy versions across production, staging, and internal deployments.
Review schedule audit logs for unauthorized create, update, run, or delete activity.
Check for unexpected schedule entries referencing server or dokploy-server types.
Confirm organization and role checks exist around schedule operations after remediation.
Review host and target-server command execution history for suspicious activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
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.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-269 · source CWE mapping
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.