CVE-2026-2977
Received Received - Intake
Unrestricted File Upload in FastApiAdmin Scheduled Task API

Publication date: 2026-02-23

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security vulnerability has been detected in FastApiAdmin up to 2.2.0. This affects the function upload_controller of the file /backend/app/api/v1/module_common/file/controller.py of the component Scheduled Task API. Such manipulation leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-23
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-02-23
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fastapiadmin fastapiadmin to 2.2.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-434 The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': 'CVE-2026-2977 is a security vulnerability in FastApiAdmin versions up to 2.2.0, specifically in the upload_controller function of the Scheduled Task API component. It allows attackers to perform unrestricted file uploads by manipulating the upload mechanism, which relies only on the Content-Type header to determine allowed file extensions without proper validation or path canonicalization.'}, {'type': 'paragraph', 'content': "Attackers can bypass file extension restrictions by disguising malicious files (for example, uploading a Python script as an SVG file), which are then saved directly to the server's upload directory. This can lead to remote code execution when combined with FastApiAdmin's scheduled task APIs."}] [2, 3]


How can this vulnerability impact me? :

This vulnerability can impact the confidentiality, integrity, and availability of your system. By exploiting it, an attacker can upload arbitrary and potentially dangerous files to your server, which may be executed remotely, leading to unauthorized code execution.

Such exploitation can result in system compromise, data breaches, service disruption, and unauthorized access to sensitive information.


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 can be detected by monitoring for unauthorized or suspicious file uploads to the endpoint /api/v1/common/file/upload, especially uploads that bypass file extension restrictions by manipulating the Content-Type header.'}, {'type': 'paragraph', 'content': 'Detection can involve checking server logs for unusual upload activity, such as files with unexpected extensions or filenames, or uploads by users with the module_common:file:upload permission.'}, {'type': 'paragraph', 'content': 'Suggested commands include searching web server access logs for POST requests to the upload endpoint and inspecting uploaded files for suspicious content or extensions.'}, {'type': 'list_item', 'content': "grep 'POST /api/v1/common/file/upload' /var/log/nginx/access.log"}, {'type': 'list_item', 'content': "find /path/to/upload/directory -type f \\( -name '*.svg' -o -name '*.py' \\) -exec file {} \\; | grep -i 'script'"}, {'type': 'list_item', 'content': 'audit logs review for users with module_common:file:upload permission performing uploads'}] [3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing strict server-side validation of uploaded files rather than relying on the Content-Type header.

  • Validate file magic bytes to confirm actual file type.
  • Derive file extensions from the actual content instead of trusting the Content-Type header.
  • Normalize and restrict file paths to a safe upload directory that disallows execution permissions.
  • Generate randomized, safe filenames for uploads to prevent overwriting or predictable file locations.
  • Implement strict allowlists for permitted upload file types.
  • Scan uploaded files for dangerous content.
  • Apply least-privilege access controls and audit logging for upload and scheduled task APIs to monitor and limit misuse.

Since no official patches or countermeasures are available, replacing the affected FastApiAdmin product with a secure alternative is recommended to avoid exploitation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart