Skip to main content
VulnerabilityPublished Updated

CVE-2024-39163: pyspider · Cross-Site Request Forgery (CSRF)

Affects pyspiderSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 0.3.11 soon.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.3.11
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 4 Dec 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

Upgrade pyspider to 0.3.11.

Affected software

ProductAffectedFixed in
PyPIpyspiderpkg:pypi/pyspiderOther threatsAffected
  • <0.3.11
Fixed in
  • 0.3.11

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

AI-suggested

To mitigate CVE-2024-39163, organizations should first monitor pyspider project communications for official patches and apply them promptly once available. In the interim, implement strict CSRF protections on all Flask endpoints by integrating CSRF tokens and validating them on the server side. Restrict access to pyspider’s web interfaces to trusted networks or VPNs to reduce exposure. Employ web application firewalls (WAFs) with rules to detect and block CSRF attack patterns. Educate users about the risks of clicking untrusted links while authenticated to pyspider services. Consider isolating pyspider instances in segmented environments to limit lateral movement if compromised. Regularly audit and review logs for suspicious requests that could indicate CSRF attempts. Finally, if feasible, disable or limit the use of web interfaces that are not essential, reducing the attack surface.

Description

binux pyspider up to v0.3.10 was discovered to contain a Cross-Site Request Forgery (CSRF) via the Flask endpoints.

References

Community reviews

Loading reviews…