dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-6841

MEDIUM · 6.5 CVSS v3.0 Published 2025-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Cross-Site Request Forgery (CSRF) vulnerability exists in the latest commit (56b782bcefd2e59b19cd7ba7878b95f54884f502) of the vanna-ai/vanna repository. Two endpoints in the built-in web app that provide SQL functionality are implemented as simple GET requests, making them susceptible to CSRF attacks. This vulnerability allows an attacker to run arbitrary SQL commands via CSRF without the target intending to expose the web app to the network or other users. The impact is limited to data alteration or deletion, as the attacker cannot read the results of the query.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

CSRF vulnerability in vanna-ai/vanna's built-in web app where two SQL functionality endpoints are implemented as simple GET requests instead of proper POST requests with CSRF protection. Attackers can trick authenticated users into executing arbitrary SQL commands for data alteration or deletion.

MitigationConvert the vulnerable GET endpoints to POST requests and implement anti-CSRF tokens to prevent cross-site request forgery attacks on SQL operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if vanna web app is running
    Check for processes listening on common web ports (5000, 8080) or inspect running Python processes for vanna app imports. Look for 'vanna' in process listings or check if the vanna web interface is accessible.
    Affected if The vanna web application is exposed and accessible.
  2. Check installed vanna version
    Run 'pip show vanna' or inspect the installed package version. Compare against any available fixed versions from the vanna-ai/vanna repository releases.
    Affected if The installed version matches or falls within an unpatched version range.
  3. Locate the SQL endpoint handlers in the codebase
    Search the vanna installation for route definitions handling SQL operations. Look for files containing SQL execution logic, typically in routes.py, api.py, or similar endpoint definition files within the vanna web app module.
    Affected if Code contains SQL operation endpoints that are defined with GET methods.
  4. Inspect endpoint method definitions
    Examine the route decorators and method handlers for the SQL functionality. Check if endpoints like '/execute-sql', '/run-query', or similar SQL-related routes accept GET requests by reviewing the @app.route() or equivalent decorations.
    Affected if SQL operation endpoints are mapped to GET methods instead of POST methods.
  5. Verify CSRF protection is absent
    Review the endpoint handlers for CSRF token validation. Check if the request handling code includes any CSRF verification logic, token checking, or anti-CSRF middleware for the SQL endpoints.
    Affected if The SQL endpoints lack CSRF token validation and accept requests without verification.

A user is affected if they are running a version of vanna with the web app where SQL operation endpoints accept GET requests without CSRF protection, allowing authenticated users to be tricked into executing malicious SQL commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Convert the vulnerable GET endpoints to POST requests and implement anti-CSRF tokens to prevent cross-site request forgery attacks on SQL operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6841 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data