Flask App Builder has an Authentication Bypass vulnerability when using non AUTH_DB methods
GHSA-765j-9r45-w2q2 · CVE-2025-58065 · PYSEC-2026-1378
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Impact
When Flask-AppBuilder is configured to use OAuth, LDAP, or other non-database authentication methods, the password reset endpoint remains registered and accessible, despite not being displayed in the user interface. This allows an enabled user to reset their password and be able to create JWT tokens even after the user is disabled on the authentication provider.
Patches
Upgrade to Flask-AppBuilder version 4.8.1 or later
Workarounds
If immediate upgrade is not possible:
- Manually disable password reset routes in the application configuration
- Implement additional access controls at the web server or proxy level to block access to the reset my password URL.
- Monitor for suspicious password reset attempts from disabled accounts
References
- WEB https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-765j-9r45-w2q2
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2025-58065
- WEB https://github.com/dpgaspar/Flask-AppBuilder/pull/2384
- WEB https://github.com/dpgaspar/Flask-AppBuilder/commit/a942a9cc5775752f9a02f97fd8198dd288fa93ee
- PACKAGE https://github.com/dpgaspar/Flask-AppBuilder
- WEB https://github.com/dpgaspar/Flask-AppBuilder/releases/tag/v4.8.1
Ready to move
Start Securing
Free, no credit card | First findings in minutes