CVE-2024-57968
Advantive VeraCore before 2024.4.2.1 allows remote authenticated users to upload files to unintended folders (e.g., ones that are accessible during web browsing by other users). upload.aspx can be used for this.
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? Partly. The vulnerability involves authenticated users uploading files via a web interface to unintended folders. A web application firewall could partially detect unusual file upload requests targeting specific parameters or paths that normal users do not use. A custom WAF rule can filter file upload to upload.aspx with unusual destination folder parameter, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.
What a custom rule would match: file upload to upload.aspx with unusual destination folder parameter
Also consider: patch · custom WAF rule · 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-57968 being exploited?
Yes. CVE-2024-57968 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-57968?
CVE-2024-57968 is rated Critical with a CVSS score of 9.9. 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-57968?
Yes. A fix has been recorded for CVE-2024-57968. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-57968 affect?
CVE-2024-57968 affects advantive:veracore. 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< 2024.4.2.1
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 14 Mar 2025 (SSVC 2.0.3).
timeline
- 3 Feb 2025Published
- 10 Mar 2025Added to CISA KEV (exploited in the wild) · 34 days later
- 14 Mar 2025CISA SSVC assessment: exploitation active · 4 days later
- 31 Mar 2025CISA remediation due date (US federal agencies) · 17 days later
- 21 Oct 2025CVE record last updated · 205 days (about 7 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkadvantive.my.site.com /support/s/article/VeraCore-Release-Notes-2024-4-2-1
- Linkintezer.com /blog/research/xe-group-exploiting-zero-days/
- Linksolissecurity.com /en-us/insights/xe-group-from-credit-card-skimming-to-exploiting-zero-days/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-57968
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.