CVE-2024-57337VulnerabilityPublished 28 May 2025Updated 30 May 2025

CVE-2024-57337: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected >=5.0.0 <=5.5.14.1070 >=7.0.0 <=7.4.3.960 >=8.0.0 <=8.2.0.345	Fixed in–

AI-suggested

European organizations should immediately identify and inventory all instances of M2Soft CROWNIX Report & ERS software in their environment, including versions 5.x, 7.x, and 8.x series. Until official patches are released, organizations should implement strict network segmentation and restrict access to the vulnerable service to trusted internal networks only. Deploy web application firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block suspicious file upload attempts targeting opcode 500 functionality. Conduct thorough monitoring and logging of file upload activities and opcode 500 usage to detect anomalous behavior indicative of exploitation attempts. Employ application-layer filtering to validate and sanitize all uploaded files, ensuring only expected file types and sizes are accepted. Additionally, consider disabling or restricting the opcode 500 functionality if it is not essential for business operations. Organizations should maintain up-to-date backups of critical data and prepare incident response plans to quickly contain and remediate any potential compromise. Once patches become available, prioritize their deployment in all affected environments.

Description

An arbitrary file upload vulnerability in the opcode 500 functionality of M2Soft CROWNIX Report & ERS v5.x to v5.5.14.1070, v7.x to v7.4.3.960, and v8.x to v8.2.0.345 allows attackers to execute arbitrary code via supplying a crafted file.

Impact

For European organizations, the impact of CVE-2024-57337 could be substantial, particularly for those relying on M2Soft CROWNIX Report & ERS software for critical reporting and enterprise resource systems. Successful exploitation could lead to unauthorized code execution, which may result in data breaches, manipulation of reports, disruption of business processes, and potential lateral movement within corporate networks. Confidentiality and integrity of sensitive business data could be compromised, affecting compliance with GDPR and other data protection regulations. The lack of required authentication and user interaction increases the risk of automated exploitation attempts, especially in environments where the vulnerable service is accessible over the network. This could lead to reputational damage, financial losses, and regulatory penalties for affected organizations. The medium CVSS score suggests that while the vulnerability is serious, exploitation may require some specific conditions or knowledge, but the absence of privileges or user interaction requirements makes it easier for attackers to attempt exploitation remotely.

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

m2soft.co.kr/sub/board/news.asp?mode=view&idx=2411 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 04:27 UTC

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats