CVE-2024-7694
ThreatSonar Anti-Ransomware from TeamT5 does not properly validate the content of uploaded files. Remote attackers with administrator privileges on the product platform can upload malicious files, which can be used to execute arbitrary system command on the server.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves uploading malicious files via the product's upload functionality, which is accessed over HTTP. However, the malicious files appear as normal uploads, so a web application firewall cannot reliably distinguish them from legitimate files.
Also consider: MIME sniff · sandbox storage
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-7694 being exploited?
Yes. CVE-2024-7694 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-7694?
CVE-2024-7694 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-7694?
Not known from our data. No patch reference has been recorded for CVE-2024-7694, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2024-7694 affect?
CVE-2024-7694 affects teamt5:threatsonar_anti-ransomware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 3.4.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 17 Feb 2026 (SSVC 2.0.3).
timeline
- 12 Aug 2024Published
- 17 Feb 2026Added to CISA KEV (exploited in the wild) · 553 days (about 2 years) later
- 17 Feb 2026CISA SSVC assessment: exploitation active · same day later
- 18 Feb 2026CVE record last updated · 1 day later
- 10 Mar 2026CISA remediation due date (US federal agencies) · 20 days later
- 2 Nov 2026Analysed by vulneraibility.com · 238 days (about 8 months) later
- Advisorytwcert.org.tw /tw/cp-132-7998-d76dd-1.html
- Advisorytwcert.org.tw /en/cp-139-8000-e5a5c-2.html
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-7694
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.