How severe is GHSA-fw5r-6m3x-rh7p?

GHSA-fw5r-6m3x-rh7p has a CVSS score of 3.6/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-fw5r-6m3x-rh7p?

GHSA-fw5r-6m3x-rh7p affects the following packages: flask-appbuilder (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-fw5r-6m3x-rh7p?

Update flask-appbuilder to 4.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fw5r-6m3x-rh7p is resolved across your whole dependency graph.

How do I detect GHSA-fw5r-6m3x-rh7p in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flask-appbuilder, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fw5r-6m3x-rh7p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-fw5r-6m3x-rh7p actively exploited in the wild?

No public exploit code has been indexed for GHSA-fw5r-6m3x-rh7p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fw5r-6m3x-rh7p?

GHSA-fw5r-6m3x-rh7p has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fw5r-6m3x-rh7p?

GHSA-fw5r-6m3x-rh7p is classified as CWE-525 (CWE-525). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fw5r-6m3x-rh7p published, and has it been updated?

GHSA-fw5r-6m3x-rh7p was published on September 4, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

Flask-AppBuilder's login form allows browser to cache sensitive fieldsGHSA-fw5r-6m3x-rh7p

LOWFix: dpgaspar/Flask-AppBuilder@3030e88

GHSA-fw5r-6m3x-rh7p is a low-severity (CVSS 3.6) CWE-525 vulnerability in flask-appbuilder. A fix is available for flask-appbuilder — see the affected versions and patch details below.

Also known asCVE-2024-45314PYSEC-2026-1382

Published

Sep 4, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fw5r-6m3x-rh7p.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍flask-appbuilder

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Flask-AppBuilder is an application development framework. Prior to version 4.5.1, the auth DB login form default cache directives allows browser to locally store sensitive data. This can be an issue on environments using shared computer resources. Version 4.5.1 contains a patch for this issue. If upgrading is not possible, configure one's web server to send the specific HTTP headers for /login per the directions provided in the GitHub Security Advisory.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`flask-appbuilder`	all versions	4.5.1`pip install --upgrade 'flask-appbuilder==4.5.1'`

Affected Products

1 product · 1 configurations

Application

flask-appbuilderdpgaspar

< 4.5.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flask-appbuilder, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flask-appbuilder to 4.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fw5r-6m3x-rh7p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Auth DB login form default cache directives allows browser to locally store sensitive data. This can be an issue on environments using shared computer resources. ### Patches Upgrade flask-appbuilder to version 4.5.1 ### Workarounds If upgrading is not possible configure your web server to send the following HTTP headers for /login: "Cache-Control": "no-store, no-cache, must-revalidate, max-age=0" "Pragma": "no-cache" "Expires": "0"