dbcve.org
InjectionWeakness · CWE-74

CVE-2025-3804

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

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 vulnerability classified as critical has been found in thautwarm vscode-diana 0.0.1. Affected is an unknown function of the file Gen.py of the component Jinja2 Template Handler. The manipulation leads to injection. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used.

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 · moderate confidence

A Jinja2 template injection vulnerability exists in vscode-diana version 0.0.1 in the Gen.py file's Jinja2 Template Handler component. The vulnerability allows for injection attacks and requires local access to exploit.

MitigationFix the template handling in Gen.py by implementing proper input sanitization/validation and using safe template rendering practices (e.g., autoescape, whitelist approaches) when processing Jinja2 templates.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Check if vscode-diana is installed
    Run 'pip show vscode-diana' or check your extension/plugin directory for vscode-diana
    Affected if vscode-diana version 0.0.1 is installed
  2. Locate the Gen.py file
    Search for Gen.py in the vscode-diana installation directory, typically under the package root or templates directory
    Affected if Gen.py exists in the vscode-diana package at version 0.0.1
  3. Inspect Gen.py for Jinja2 template handling
    Open Gen.py and search for Jinja2 imports (e Environment, Template) or template rendering calls
    Affected if Gen.py contains Jinja2 template rendering code using Environment or Template classes without sanitization
  4. Verify template injection input path
    Examine how user input flows into the template rendering in Gen.py - check for template.render() or environment.from_string() calls receiving raw input
    Affected if Raw user input or unsanitized variables are passed directly to Jinja2 template rendering functions

If vscode-diana version 0.0.1 is installed with Gen.py containing Jinja2 template handling that accepts unsanitized input, the environment is affected by CVE-2025-3804.

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

Fix the template handling in Gen.py by implementing proper input sanitization/validation and using safe template rendering practices (e.g., autoescape, whitelist approaches) when processing Jinja2 templates.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3804 — 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-2025-3804 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