Authenticated command execution via unsanitized cron task
Published Dec 19, 2025 · Updated Dec 19, 2025
OS command injection in BrainyCP 1.0 allows remote authenticated users to execute arbitrary commands through its crontab interface. The addcron action accepts the cron_command parameter and places its value in a scheduled task without neutralizing shell syntax. A valid panel login is required; cron subsequently invokes the submitted command under the selected cron user, enabling host command execution.
Summary
What happened
OS command injection in BrainyCP 1.0 allows remote authenticated users to execute arbitrary commands through its crontab interface. The addcron action accepts the cron_command parameter and places its value in a scheduled task without neutralizing shell syntax. A valid panel login is required; cron subsequently invokes the submitted command under the selected cron user, enabling host command execution.
The record
- CVE
- CVE-2023-53945
- Published
- Dec 19, 2025
- Updated
- Dec 19, 2025
- Vendor
- BrainyCP
- Product
- BrainyCP
- Classifications
- CWE-78, T1053.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 19, 2025CVE publishedPublication date reported by the CVE source.
- Dec 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BrainyCP V1.0 - Remote Code Executionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo