VulnerabilityPublished 1 May 2024Updated 2 Aug 2024

CVE-2024-32210: LoMag WareHouse Management application · Use of Hard-coded Password

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: None: There is no loss of integrity within 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 1 May 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate CVE-2024-32210, organizations should immediately assess their deployment of LoMag WareHouse Management application versions 1.0.20.120 or older. Since no official patches are currently available, the following specific actions are recommended: 1) Restrict network access to the application and its database servers using firewalls and network segmentation to limit exposure to trusted internal networks only. 2) Conduct a thorough credential audit to identify and change any hard-coded or default passwords in configuration files or application code where possible. 3) Implement application-layer access controls and monitoring to detect unauthorized access attempts. 4) If feasible, upgrade to a newer version of the software once a patch or update addressing this vulnerability is released. 5) Employ database activity monitoring to detect anomalous queries or connections that may indicate exploitation attempts. 6) Educate IT and security teams about the risks of hard-coded credentials and enforce secure coding practices for future deployments. 7) Consider deploying Web Application Firewalls (WAFs) or Intrusion Detection Systems (IDS) to provide additional layers of defense against exploitation attempts. These targeted measures go beyond generic advice by focusing on immediate containment and detection in the absence of an official patch.

Description

The LoMag WareHouse Management application version 1.0.20.120 and older were to utilize hard-coded passwords by default for forms and SQL connections.

Impact

The primary impact of CVE-2024-32210 is unauthorized disclosure of sensitive information managed by the LoMag WareHouse Management application. Attackers exploiting this vulnerability can access data without proper authentication, potentially exposing inventory details, client information, and operational data. While the vulnerability does not allow modification or deletion of data, the confidentiality breach can facilitate further attacks such as social engineering, competitive intelligence gathering, or supply chain disruption. Organizations relying on this application for warehouse and inventory management may face operational risks if sensitive data is leaked. Additionally, regulatory compliance issues may arise due to exposure of protected or confidential information. The ease of exploitation and remote accessibility increase the likelihood of opportunistic attacks, especially in environments where the application is accessible from external or less trusted networks. The absence of known exploits in the wild suggests limited current targeting, but the vulnerability remains a latent risk until remediated.

CWE-259Use of Hard-coded Password (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
Architecture and Design
For outbound authentication: store passwords outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password.
Architecture and Design
Perform access control checks and limit which entities can access the feature that requires the hard-coded password. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gainsec.com/2024/04/28/cve-2024-32210-cve-2024-32211-cve-2024-32212-cve-2024-32213-lomag-integrator-ce-warehouse-management/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:12 UTC

WeaknessesCWE-259

Technical details

References

Community reviews

Related threats