Skip to main content
VulnerabilityPublished Updated

CVE-2023-49438: flask-security-too

Affects flask-security-tooSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei).

Data as of 26 Oct 2026, 10:12 UTC

Severity
Medium

Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA

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.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Dec 2023

  2. Detectable: evidence found.

    nuclei template: Python Flask-Security-Too <=5.3.2 - Open Redirect

  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

Affected software

ProductAffectedFixed in
PyPIflask-security-toopkg:pypi/flask-security-tooOther threatsAffected
  • <=5.3.2
Fixed in–

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

AI-suggested

Users should monitor the vendor advisory for updates. Until a fix is available, avoid using untrusted URLs in the 'next' parameter or implement custom validation to restrict redirect targets to trusted domains.

Description

An open redirect vulnerability exists in the Python package Flask-Security-Too versions up to and including 5.3.2. This flaw allows attackers to craft URLs that abuse the 'next' parameter on the /login and /register routes to redirect users to malicious websites.

References

Community reviews

Loading reviews…