Skip to main content
VulnerabilityPublished Updated

CVE-2024-41577: Ueditor component of productinfoquick · An Arbitrary File Upload

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 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

1. Immediately audit all instances of productinfoquick v1.0 to identify deployments using the vulnerable Ueditor component. 2. Implement strict input validation and file type verification on the server side to block uploads of files that do not conform to expected image formats, including checking file headers and MIME types beyond file extensions. 3. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious file upload attempts, especially those containing embedded executable code within image files. 4. Restrict file upload directories with proper permissions and isolate them from executable paths to prevent execution of uploaded files. 5. Monitor logs and network traffic for unusual upload activity or execution attempts originating from uploaded files. 6. If possible, disable or limit file upload functionality until an official patch is released. 7. Engage with the vendor or community to obtain updates or patches as soon as they become available. 8. Conduct regular security assessments and penetration testing focused on file upload mechanisms. 9. Educate development and security teams about the risks of unrestricted file uploads and secure coding practices to prevent similar vulnerabilities.

Description

An arbitrary file upload vulnerability in the Ueditor component of productinfoquick v1.0 allows attackers to execute arbitrary code via uploading a crafted PNG file.

References

Community reviews

Loading reviews…