Skip to content
Noroxi
CVE-2015-6938· NVD / CVE Program· CNA mitre

Cross-site scripting (XSS) vulnerability in the file browser in notebook/notebookapp.py in IPython Notebook before 3.2.2 and Jupyter Noteboo

Cross-site scripting (XSS) vulnerability in the file browser in notebook/notebookapp.py in IPython Notebook before 3.2.2 and Jupyter Notebook 4.0.x before 4.0.5 allows remote attackers to inject arbitrary web script or HTML via a folder name. NOTE: this was originally reported as a cross-site request forgery (CSRF) vulnerability, but this may be inaccurate.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Sep 21, 2015
Updated
Jun 16, 2026
EPSS
2.8% · 86th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.8%

Affected systems

VendorProduct
jupyternotebook
fedoraprojectfedora
opensuseopensuse
ipythonnotebook

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora21
  • fedoraproject fedora22
  • fedoraproject fedora23
  • ipython notebookup to 3.2.1 inclusive
  • jupyter notebook4.0.0
  • jupyter notebook4.0.1
  • jupyter notebook4.0.2
  • jupyter notebook4.0.3
  • jupyter notebook4.0.4
  • opensuse opensuse13.1
  • opensuse opensuse13.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12ipythonbefore 2.4.1-12.4.1-1
PyPIipythonbefore 3.2.23.2.2
PyPInotebookfrom 4.0.0 · before 4.0.54.0.5

Other highest-scoring records for the same primary product.

  • CVE-2021-32798Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in notebook
    39Monitor
  • CVE-2026-40171Jupyter Notebook and JupyterLab token theft via stored XSS in help command linker
    33Monitor
  • CVE-2018-8768In Jupyter Notebook before 5.4.1, a maliciously forged notebook file can bypass sanitization to execute JavaScript in the notebook context.
    31Monitor
  • CVE-2022-24758Insertion of Sensitive Information into Log File affects Jupyter Notebook
    30Monitor
  • CVE-2020-26215Open redirect in Jupyter Notebook
    24Monitor
  • CVE-2019-10856In Jupyter Notebook before 5.7.8, an open redirect can occur via an empty netloc.
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ipython2.4.1-1 · Debian:12Package registry (OSV)
PyPI:ipython3.2.2Package registry (OSV)
PyPI:notebook4.0.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:P/A:N

    nvd-primary

    Root cause

    User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    commentEl.innerHTML = comment.body;

    Fixed

    ts
    commentEl.textContent = comment.body;

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records