CVE-2024-50620
Unrestricted File Upload in CIPPlanner CIPAce Enables Code Execution
Publication date: 2026-02-11
Last updated on: 2026-02-20
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cipplanner | cipace | to 9.17 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2024-50620 is a security vulnerability in CIPPlanner Corporationβs CIPAce software versions before 9.17. It involves an unrestricted upload of files with dangerous types in the rich text editor and document management components.
Specifically, authorized users can upload executable files when inserting images in the rich text editor or when uploading files on the document management page. If these executable files are stored in directories that allow execution, they can be run, which poses a security risk.
How can this vulnerability impact me? :
This vulnerability can allow an authorized user to upload and potentially execute malicious executable files within the application environment.
If exploited, it could lead to unauthorized code execution, compromising the integrity and availability of the system.
However, an investigation found no significant operational impact or security breach in reported incidents, likely due to existing security protocols and operational best practices.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability involves the unrestricted upload of executable files through the rich text editor and document management components in CIPPlanner CIPAce before version 9.17. Detection can focus on identifying unauthorized or suspicious executable files uploaded to the system, especially in directories where uploaded files are stored.'}, {'type': 'paragraph', 'content': 'To detect this vulnerability on your system, you can scan the upload directories for executable files that should not be present. For example, on a Linux system, you might use commands like:'}, {'type': 'list_item', 'content': 'find /path/to/upload/directory -type f \\( -name "*.exe" -o -name "*.bat" -o -name "*.sh" -o -name "*.cmd" \\) -ls'}, {'type': 'list_item', 'content': 'Check web server logs for unusual file upload activity or uploads of executable file types.'}, {'type': 'list_item', 'content': 'Use application-level logging or monitoring to track file uploads through the rich text editor and document management pages.'}, {'type': 'paragraph', 'content': 'Since the vulnerability requires an authorized user to upload executable files, monitoring user upload behavior and permissions can also help detect potential exploitation.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting the types of files that can be uploaded through the rich text editor and document management components to a safe whitelist of allowed file types.
CIPPlannerβs official remediation involves implementing a whitelist that excludes executable files. The default whitelist includes file types such as 7z, avi, bmp, csv, doc, docx, dotm, dotx, dwg, gif, jpeg, jpg, mov, mp3, mp4, mpp, msg, pdf, png, ppt, pptx, txt, wav, wmv, xls, xlsx, and zip.
Additional immediate steps include:
- Apply any available patches or upgrades from CIPPlanner to version 9.17 or later, where the vulnerability is fixed.
- Review and restrict execute permissions on directories where uploaded files are stored to prevent execution of any uploaded executables.
- Monitor and audit authorized user accounts to detect any suspicious upload activity.
- Consider additional security controls such as Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and penetration testing as recommended by CIPPlanner.