Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:NSummary
CVE-2025-1473 is a high-severity CSRF (CWE-352) vulnerability in Lfprojects Mlflow. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as Other Platforms; in the Other ATLAS/OWASP Terms risk domain.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-1473 is a Cross-Site Request Forgery (CSRF) vulnerability, classified under CWE-352, affecting the Signup feature in mlflow/mlflow versions 2.17.0 through 2.20.1. Published on 2025-03-20, it has a CVSS v3.1 base score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N). The flaw enables unauthorized account creation through forged requests.
An attacker with network access and no required privileges can exploit this by tricking an authenticated user into interacting with a malicious webpage or link (UI:R), such as clicking a button that submits a CSRF payload to the vulnerable Signup endpoint. Successful exploitation creates a new account under the attacker's control, which can then be used to perform unauthorized actions, potentially leading to high confidentiality impact through data access and low integrity impact via limited modifications.
Mitigation details are available in the project's GitHub commit ecfa61cb43d3303589f3b5834fd95991c9706628, which patches the issue, and via the Huntr bounty report at https://huntr.com/bounties/43dc50b6-7d1e-41b9-9f97-f28809df1d45. Security practitioners should upgrade to a fixed version beyond 2.20.1 and review CSRF protections in MLflow deployments.
Mlflow is an open-source platform for managing the machine learning lifecycle, making this vulnerability relevant to AI/ML environments where unauthorized account creation could compromise experiment tracking, model registries, or deployment workflows. No public evidence of real-world exploitation is noted in the provided details.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6808
Vulnerability Data
A Cross-Site Request Forgery (CSRF) vulnerability exists in the Signup feature of mlflow/mlflow versions 2.17.0 to 2.20.1. This vulnerability allows an attacker to create a new account, which may be used to perform unauthorized actions on behalf of the malicious…
more
user.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Other Platforms
- Risk Domain
- Other ATLAS/OWASP Terms
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: mlflow
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.
Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.