Skip to main content
VulnerabilityPublished Updated

CVE-2024-42577: Warehouse Inventory System · Cross-Site Request Forgery (CSRF)

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

AI-suggested

To mitigate CVE-2024-42577, organizations should implement several specific measures beyond generic advice: 1) Apply strict anti-CSRF protections by integrating unique, unpredictable CSRF tokens in all state-changing requests, especially in add_product.php. 2) Validate the HTTP Referer and Origin headers to ensure requests originate from trusted sources. 3) Enforce least privilege principles by restricting user permissions to only necessary functions, minimizing the impact of potential exploitation. 4) Implement multi-factor authentication (MFA) to reduce the risk of session hijacking or unauthorized access. 5) Monitor web application logs for unusual or repeated requests to add_product.php that could indicate exploitation attempts. 6) Educate users about phishing and social engineering risks to reduce the likelihood of user interaction exploitation. 7) If possible, isolate the Warehouse Inventory System behind a VPN or internal network to limit exposure. 8) Engage with the vendor or development team to request or develop patches addressing the CSRF vulnerability. 9) Conduct regular security assessments and penetration tests focusing on CSRF and session management weaknesses. These targeted actions will reduce the attack surface and help prevent exploitation until official patches are available.

Description

A Cross-Site Request Forgery (CSRF) in the component add_product.php of Warehouse Inventory System v2.0 allows attackers to escalate privileges.

References

Community reviews

Loading reviews…