Skip to content
Fencer Intel
high 8.8

CVE-2015-5607 json

IPython vulnerable to cross site request forgery (CSRF)

published 2017-09-20 9 y ago modified 2026-06-17 4 mo ago also GHSA-7fc2-rm35-2pp7 , PYSEC-2017-47 , EUVD-2017-0064

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

Cross-site request forgery in the REST API in IPython 2 and 3.

Patch / fix

  • pypi ipython 2.4.1, 3.2.1, 3.2.3
  • ipython Debian 14, Debian 13, Debian 12 2.4.1-1

debian advisories DEBIAN-CVE-2015-5607

  • ipython Ubuntu Pro 14.04 LTS 1.2.1-2ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2015-5607

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-5607 updated cvss 4.3

iptyhon: cross-site request forgery in get_origin()

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • openwall.com http://www.openwall.com/lists/oss-security/2015/07/21/3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi ipython
>=0.12, <2.4.1
>=3.0.0, <3.2.3
<3.2.1
2.4.1
3.2.3
3.2.1

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.