PatchTheCVECVE-2023-1516: RoboDK versions 5.5.3 and prior contain an insecure permission assignment to critical directories vulnerabili
CVE-2023-1516 is a high-severity flaw (CVSS 7.9) affecting robodk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
RoboDK versions 5.5.3 and prior contain an insecure permission assignment to critical directories vulnerability, which could allow a local user to escalate privileges and write files to the RoboDK process and achieve code execution.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.9 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 92%) |
| CISA exploited list | No |
| Weakness | CWE-732 |
| Published | 2023-03-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-1516?
robodk: upgrade to newer than 5.5.3. Exact commands for each OS are on this page.
Is CVE-2023-1516 being exploited?
CVE-2023-1516 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-1516 affect?
CVE-2023-1516 affects robodk. Severity is high (CVSS 7.9). RoboDK versions 5.5.3 and prior contain an insecure permission assignment to critical directories vulnerability, which could allow a local user to escalate privileges and write files to the RoboDK process and achieve code execution.
How urgent is CVE-2023-1516?
Priority 30/100. High severity