CriticalCVE-2024-57968

    Advantive VeraCore Unrestricted File Upload Vulnerability (CVE-2024-57968)

    Published In CISA KEV since Sources: CVE.org, pwn.watch

    Share

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. Update Advantive VeraCore to version 2024.4.2.1. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Advantive VeraCore lt *..2024.4.2.1
    Fixed in
    • Advantive VeraCore 2024.4.2.1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.9

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    9.9

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, pwn.watch

    32.3 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 98.3

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    234.51 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.9 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.9
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    32.3 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    98.3
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 14 March 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-434

    Response and mitigation

    Why act now?

    Prioritisation rationale

    VeraCore is an order-fulfilment and warehouse-management platform that is usually internet-facing and holds customer, order and shipping data, which makes retailers, 3PLs and fulfilment providers the core target profile. The flaw is network-reachable with low complexity and needs at most a low-privileged account, or none according to CISA. Uploaded webshells give full compromise of confidentiality, integrity and availability, and its exploitation likelihood ranks among the highest of all scored CVEs. CISA has no known ransomware use on record, but the observed tradecraft favours quiet, long-term persistence. Treat any internet-exposed, unpatched VeraCore as critical with a 24 h patch target, and run a retrospective webshell hunt even on hosts you have already patched.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch now: Upgrade every VeraCore instance to version 2024.4.2.1 or later. All earlier builds are vulnerable. If you can't get a maintenance window today, start the controls under "Mitigation layers" immediately.
      • Cut exposure: Block direct internet access to the VeraCore web front end (IIS, typically TCP 443/80) until it is patched. Allow access only via VPN or a source-IP allowlist for customer, warehouse and partner networks. CISA describes the flaw as exploitable without authentication, while NVD says authenticated. Plan for the worse case.
      • Hunt before you patch: Sweep the webroot and every browser-reachable directory for new or modified .aspx, .ashx, .asmx, .asp, .config and .dll files. Patching does not remove a webshell that is already in place. Preserve evidence (hash, timestamps, IIS logs) before you delete anything.
      • Rotate credentials: On suspicion or confirmation, reset all VeraCore accounts with upload rights. Also rotate the database connection strings in web.config, the app-pool identity, service accounts, and API keys used for ERP or carrier integrations.
      • Account hygiene: Disable unused, shared and default VeraCore accounts and force password resets for privileged users. Even in the authenticated reading of this flaw, a single low-privileged account is all an attacker needs.
      • Regulatory clock: If you confirm a compromise, the NIS2 early-warning deadline is 24 h to BSI or your national CSIRT. Check GDPR Art. 33 as well if customer data is involved.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place the VeraCore server in a DMZ or dedicated segment. Restrict its egress to the destinations it needs (database, defined partner APIs) and block general internet egress to kill webshell callbacks and exfiltration paths. Deny lateral connections from the web server into office and AD networks (SMB 445, RDP 3389, WinRM 5985/5986).
      • WAF / reverse proxy rule: Allow POST requests to upload.aspx only from trusted source ranges. Block multipart uploads where filename= matches executable extensions (\.(aspx|ashx|asmx|asp|config|cshtml|dll|exe|ps1|bat)$). Also block traversal patterns in upload parameters (\.\./, %2e%2e, ..\).
      • IIS hardening: Remove script and execute permissions from every upload and data directory, either by disabling "Script/Execute" in Handler Mappings or with <handlers accessPolicy="Read" />. Use Request Filtering to deny .aspx/.ashx execution in those paths.
      • Endpoint hardening: Use NTFS permissions to stop the app-pool identity writing anywhere in the webroot outside its intended upload folders. Enable EDR or ASR rules that block or alert on child processes of w3wp.exe, and add AppLocker/WDAC policies for script interpreters on the host.
      • IAM / least privilege: Limit VeraCore upload functions to roles with a genuine business need. Where feasible, enforce MFA in front of the portal, for example through an SSO-enabled reverse proxy.

    3. Runbook step 3

      Detection rules

      • IIS access logs: Look for a POST to /upload.aspx followed by a GET from the same or a new source IP to a previously unseen .aspx/.ashx file that returns 200. Example SPL: index=iis cs_method=POST cs_uri_stem="*upload.aspx" | join c_ip [search index=iis cs_method=GET cs_uri_stem="*.aspx" NOT cs_uri_stem IN (<known pages>)].
      • Sysmon EID 11 (FileCreate): Alert where Image ends with \w3wp.exe and TargetFilename ends with .aspx|.ashx|.asmx|.config|.dll under inetpub or the VeraCore install path. Sigma shape: logsource: windows/file_event; selection: Image|endswith: '\w3wp.exe' AND TargetFilename|endswith: ['.aspx','.ashx'].
      • Process ancestry (Sysmon EID 1 / Security 4688 / EDR): Alert when w3wp.exe spawns cmd.exe, powershell.exe, whoami.exe, net.exe, certutil.exe, rundll32.exe or csc.exe. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "w3wp.exe" and FileName in~ ("cmd.exe","powershell.exe","whoami.exe","certutil.exe","net.exe").
      • Network telemetry (Zeek/Suricata): Watch for new outbound connections from the VeraCore host to unfamiliar external IPs, unusually large HTTP responses to external clients (exfiltration), and SMB/RDP sessions from the web server into internal ranges.
      • Authentication: Flag VeraCore logins from unusual geolocations or ASNs shortly before upload events. New local Windows accounts (Security EID 4720) and scheduled tasks (EID 4698) on the server are also indicators.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE), pwn.watch

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    AdvantiveVeraCore
    • < 2024.4.2.1
    • 2024.4.2.1
    advantiveveracore
    • < 2024.4.2.1
    • 2024.4.2.1

    Weakness classes (CWE)

    • CWE-434Unrestricted Upload of File with Dangerous Type

      Base

      The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.

      Entry at MITRE CWE-434

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • advantive.my.site.comAdvantive advisory: Advantive VeraCorePermissions required, Product, Release notes, pwn-watch
    • intezer.comblog/research/xe-group-exploiting-zero-daysExploit, Technical description, Third-party advisory
    • solissecurity.comen-us/insights/xe-group-from-credit-card-skimming-to-exploiting…Exploit, Technical description, Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-57968government-resource, US government resource
    • pwn.watchpwn.watch: Advantive VeraCore: 2 exploited vulnerabilities (CVE-2024-57968, CVE-2025-25181)pwn-watch
    • advantive.my.site.comAdvantive advisory: Advantive VeraCorepwn-watch
    • NVD (NIST)NVD: CVE-2024-57968pwn-watch
    • NVD (NIST)NVD: CVE-2025-25181pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-57968
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-57968"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-57968.svg?lang=en" alt="CVE-2024-57968 – NEOSEC Intel" height="20"></a>