VulnerabilityPublished 28 Feb 2024Updated 27 Oct 2026

CVE-2024-25128: Flask-AppBuilder vulnerable to incorrect authentication when using auth type OpenID

Affects Flask-AppBuilderSource GCVE Database

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.3.11 as a priority.

Data as of 27 Oct 2026, 17:30 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.3.11

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Flask-AppBuilder to 4.3.11.

Affected software

Product	Affected	Fixed in
PyPIFlask-AppBuilder	Affected <4.3.11	Fixed in 4.3.11

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

AI-suggested

Upgrade Flask-AppBuilder to version 4.3.11 or later, where this vulnerability is fixed. If upgrading is not immediately possible, apply the provided workaround by customizing the authentication view to validate OpenID URLs against a whitelist of known providers, preventing acceptance of arbitrary OpenID services. No other actions are specifically required beyond these targeted mitigations.

Description

Flask-AppBuilder versions prior to 4.3.11 using the deprecated OpenID 2.0 authentication protocol (AUTH_TYPE AUTH_OID) are vulnerable to incorrect authentication. An attacker can forge HTTP requests to trick the backend into accepting any OpenID service, potentially gaining unauthorized privileged access if a malicious OpenID provider is accessible. This vulnerability is critical and has a CVSS score of 9.1. The issue is fixed in version 4.3.11. A workaround is available for those unable to upgrade immediately.

Impact

Successful exploitation grants an attacker unauthorized privileged access to the Flask-AppBuilder application by bypassing authentication controls when using the deprecated OpenID 2.0 protocol. This can lead to full compromise of the affected application without requiring user interaction or privileges. The vulnerability is rated critical with a CVSS 3.1 score of 9.1, reflecting its network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality and integrity impact.

Summary

CVE-2024-25128 affects Flask-AppBuilder when configured with AUTH_TYPE AUTH_OID using the legacy OpenID 2.0 protocol. The vulnerability allows an attacker to forge HTTP requests that cause the backend to accept arbitrary OpenID services, enabling unauthorized privilege escalation if a custom OpenID provider controlled by the attacker is reachable. This flaw arises from improper authentication validation in the OpenID 2.0 implementation. The vulnerability is mitigated by upgrading to Flask-AppBuilder 4.3.11 or applying a provided workaround patch that restricts accepted OpenID URLs to known providers.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 17:30 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats