Sage X3 version 12.14.0.50-0 is vulnerable to CSV Injection.
Product
sage x3 vulnerabilities
6 published CVES affecting sage x3, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 1
- High
- 2
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest sage x3 CVEs
Newest publication first
-
HighCVSS 7.2 EPSS 0.75%
-
MediumCVSS 5.4 EPSS 0.35%
Sage X3 version 12.14.0.50-0 is vulnerable to Cross Site Scripting (XSS). Some parts of the Web application are dynamically built using user's inputs. Yet, those inputs are not verified nor filtered by the application, so they mathed the expected format. Therefore, when HTML/Java...
-
MediumCVSS 5.4 EPSS 0.60%
Sage X3 Stored XSS Vulnerability on ‘Edit’ Page of User Profile. An authenticated user can pass XSS strings the "First Name," "Last Name," and "Email Address" fields of this web application component. Updates are available for on-premises versions of Version 12 (components shippe...
-
CVE-2020-7389 Sage X3 Syracuse Missing Authentication for Critical Function in Developer Environment
PublishedHighCVSS 7.2 EPSS 2.1%Sage X3 System CHAINE Variable Script Command Injection. An authenticated user with developer access can pass OS commands via this variable used by the web application. Note, this developer configuration should not be deployed in production.
-
CriticalCVSS 9.8 EPSS 69.4% Framework module
Sage X3 Unauthenticated Remote Command Execution (RCE) as SYSTEM in AdxDSrv.exe component. By editing the client side authentication request, an attacker can bypass credential validation. While exploiting this does require knowledge of the installation path, that information can...
-
MediumCVSS 5.3 EPSS 34.3% Framework module
Sage X3 Installation Pathname Disclosure. A specially crafted packet can elicit a response from the AdxDSrv.exe component that reveals the installation directory of the product. Note that this vulnerability can be combined with CVE-2020-7388 to achieve full RCE. This issue was fi...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.