CVE-2025-50572
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-50572 is a high-severity Improper Neutralization of Formula Elements in a CSV File (CWE-1236) vulnerability in Archerirm (inferred from references). Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-15 (Information Output Filtering) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-50572 is a vulnerability in Archer version 6.11.00204.10014 that enables attackers to execute arbitrary code through crafted system inputs. These inputs are exported into CSV files, where they can be executed when a user opens the file using compatible applications such as spreadsheet software. The issue is classified under CWE-1236 and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H), indicating high severity due to its potential for significant confidentiality, integrity, and availability impacts. The vulnerability was published on 2025-07-31.
An unauthenticated remote attacker with network access can exploit this vulnerability with low complexity by submitting malicious inputs into the system. Exploitation requires user interaction, specifically a targeted user opening the exported CSV file in a vulnerable application. Successful exploitation allows the attacker to achieve arbitrary code execution on the victim's system, potentially leading to full compromise including data theft, malware deployment, or further lateral movement.
Advisories and references, including those from archer.com, rsa.com, a GitHub repository detailing CSV injection for command execution (github.com/shorooq-hummdi/Archer-csv-injection-command-exec), and an Archer IRM community blog on formula injection in RSA Archer 6.1.x and higher, provide technical details on the issue. Notably, the supplier does not accept this as a valid vulnerability report against their product, and no specific patches or mitigations are detailed in the available information.
In context, this appears to be a disputed CSV injection vector without confirmed real-world exploitation reports in the provided data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-23301
Vulnerability Data
Archer 6.11.00204.10014 allows attackers to execute arbitrary code via crafted system inputs that would be exported into the CSV and be executed after the user opened the file with compatible applications. NOTE: the Supplier does not accept this as a…
more
valid vulnerability report against their product.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.10
Mitigating Controls (NIST 800-53 r5) AI
Output filtering/validation directly stops unneutralized formula elements from being written into CSV files.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require output neutralization for untrusted CSV content to block formula injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect formula injection but does not itself implement the mitigation.
Secure SDLC mandates input validation and output encoding that directly prevents formula injection in CSV exports.
Application security requirements include rules for safe CSV generation and handling of untrusted data.
Secure architecture principles encourage safe data export design but do not specifically address CSV formula neutralization.
Secure coding standards explicitly require neutralization of special characters when writing CSV files.