Skip to main content
CVE-2024-40318VulnerabilityPublished Updated

CVE-2024-40318: qloapps · n/a

Affects qloappsSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 07:57 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubwebkul/qloappspkg:github/webkul/qloappsOther threatsAffected
  • =1.6.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict file upload permissions to only trusted, authenticated users with a legitimate need. 2. Implement strict server-side validation of uploaded files, including checking file types, extensions, MIME types, and scanning for malicious content. 3. Employ allowlists for acceptable file formats and reject all others. 4. Use sandboxing or isolated environments to handle file uploads to prevent direct execution on production servers. 5. Monitor server logs and file upload directories for unusual or unauthorized files. 6. Apply network segmentation to limit access to critical systems running Qloapps. 7. Regularly update and patch the software once an official fix is released by Webkul. 8. Conduct security audits and penetration testing focused on file upload functionalities. 9. Educate administrators and users about the risks of arbitrary file uploads and enforce strong authentication and authorization controls. 10. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block malicious file upload attempts.

Description

An arbitrary file upload vulnerability in Webkul Qloapps v1.6.0.0 allows attackers to execute arbitrary code via uploading a crafted file.

References

Community reviews

Loading reviews…