Skip to main content
CVE-2023-47890VulnerabilityPublished Updated

CVE-2023-47890: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 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
PyPIpyloadpkg:pypi/pyloadOther threatsAffected
  • =0.5.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. Immediate upgrade or patching: Organizations should monitor for official patches or updates from pyLoad maintainers and apply them promptly once available. 2. Access control hardening: Restrict privileges of accounts running pyLoad to the minimum necessary to limit exploitation scope. 3. Input validation and filtering: Implement additional file upload validation mechanisms at the network or application layer to detect and block suspicious uploads. 4. Network segmentation: Isolate systems running pyLoad from critical infrastructure to contain potential breaches. 5. Monitoring and alerting: Deploy file integrity monitoring and anomaly detection to identify unauthorized file uploads or modifications. 6. Incident response readiness: Prepare response plans specifically addressing file upload abuse and potential malware deployment. 7. Alternative solutions: Evaluate the use of alternative download managers with better security track records if patching is delayed.

Description

pyLoad 0.5.0 is vulnerable to Unrestricted File Upload.

References

Community reviews

Loading reviews…