Check these three things.
-
System owner: confirm Dokploy servers run version 0.31.1 or later.
What to confirm
- Check every Dokploy server, including test and staging servers.
- The CVE record and the vendor advisory both list versions before 0.31.1 as affected.
- The vendor advisory lists 0.31.1 as the patched version.
- Record these evidence fields:
- Installed version.
- Where the version was read.
- Date it was read.
-
Security owner: confirm who can sign in to Dokploy servers before 0.31.1 as a member, from any network.
When the risk applies
- Exploitation needs an authenticated organization member account. Admin or owner rights are not needed.
- The member needs access to at least one project. The vendor advisory says a valid backup destination ID is also needed.
- The injected value runs when a scheduled backup runs. The vendor advisory says the default schedule is every minute.
- Host takeover also needs the Docker socket mounted into Dokploy. The vendor advisory says standard installations do this.
- Public exposure of the Dokploy sign-in and API is unknown. A network attack vector does not show that any installation is reachable from the internet.
- A reachable sign-in page alone proves neither that the server is vulnerable nor that it is safe. The installed version and the member accounts decide that.
- Records needed:
- List of member accounts, including shared accounts, automation accounts and former staff.
- Firewall, reverse proxy or load balancer settings that show who can reach the Dokploy address.
- Container settings that show whether the Docker socket is mounted into Dokploy.
-
Operations owner: check Dokploy backup service names and host activity for signs of injected commands.
What the records can show
- Stored backup settings:
- Compose backup entries whose service name contains quotes, semicolons, dollar signs or other shell characters.
- Backups created or changed by member accounts through backup.create or backup.update.
- Host records around scheduled backup runs:
- Unexplained commands run as root in the Dokploy container.
- New containers or unexpected outbound connections from the Dokploy host.
- The sources name stored backup service values as the direct sign. The host signs are reasonable places to look, not source-confirmed indicators.
- Missing logs do not prove nothing happened. An update does not rule out earlier harm.
- If the records show injected commands, escalate to the Security owner to start incident response now.
- Stored backup settings:
Update any Dokploy server before 0.31.1 that has member accounts. Then review its backup settings for injected commands.