{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5276 exists.","fix":"No fix has been published for CVE-2024-5276 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5276 is a critical SQL injection vulnerability in Fortra FileCatalyst Workflow, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-5276 and fix it if it is affected.\n\nWhat it is: CVE-2024-5276 is a critical SQL injection vulnerability in Fortra FileCatalyst Workflow, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5276 exists.\n\nAffected product: Fortra FileCatalyst Workflow. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-5276/ (Markdown: https://insights.sbomify.com/CVE-2024-5276/index.md)","id":"CVE-2024-5276","markdown":"https://insights.sbomify.com/CVE-2024-5276/index.md","name":"CVE-2024-5276","record":{"aliases":["GHSA-mgcv-6r68-pw73"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"FileCatalyst Workflow","requires_auth":"none","summary":"An attacker can modify application data and potentially create admin users via SQL injection in FileCatalyst Workflow, especially if anonymous access is enabled.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Fortra","cpe":[{"product":"filecatalyst_workflow","vendor":"fortra"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A SQL Injection vulnerability in Fortra FileCatalyst Workflow allows an attacker to modify application data.  Likely impacts include creation of administrative users and deletion or modification of data in the application database. Data exfiltration via SQL injection is not possible using this vulnerability. Successful unauthenticated exploitation requires a Workflow system with anonymous access enabled, otherwise an authenticated user is required. This issue affects all versions of FileCatalyst Workflow from 5.1.6 Build 135 and earlier.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-06-25","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":1,"refs":[{"date":"2024-06-25","kind":"metasploit","ref":"auxiliary/admin/http/fortra_filecatalyst_workflow_sqli","stars":null,"title":"Fortra FileCatalyst Workflow SQL Injection (CVE-2024-5276)"},{"date":null,"kind":"nuclei","ref":"http/cves/2024/CVE-2024-5276.yaml","stars":null,"title":"Fortra FileCatalyst Workflow \u003c= v5.1.6 - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL Injection Vulnerability in FileCatalyst Workflow 5.1.6 Build 135 (and earlier)","id":"CVE-2024-5276","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Weak Password Recovery Mechanism in lunary-ai/lunary","id":"CVE-2024-5277"},"packages":[],"prev":{"headline":"Hardcoded credentials in FileCatalyst Direct","id":"CVE-2024-5275"},"products":["FileCatalyst Workflow"],"published":"2024-06-25","related":[{"cvss_score":9.8,"headline":"Insecure Default in FileCatalyst Workflow 5.1.6 Build 139 (and earlier)","id":"CVE-2024-6633","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":9.8,"headline":"Remote Code Execution in FileCatalyst Workflow 5.x prior to 5.1.6 Build 114","id":"CVE-2024-25153","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":7.2,"headline":"SQL Injection in FileCatalyst Workflow 5.1.6 Build 139 (and earlier)","id":"CVE-2024-6632","kev_date_added":null,"published":"2024-08-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Fortra"]},"summary":"An attacker can modify application data and potentially create admin users via SQL injection in FileCatalyst Workflow, especially if anonymous access is enabled.","url":"https://insights.sbomify.com/CVE-2024-5276/"}