dbcve.org
JinjaApplication · Palletsprojects

CVE-2024-22195

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to 3.1.3 or later.
See remediation →
68/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
Jinja is an extensible templating engine. Special placeholders in the template allow writing code similar to Python syntax. It is possible to inject arbitrary HTML attributes into the rendered HTML template, potentially leading to Cross-Site Scripting (XSS). The Jinja `xmlattr` filter can be abused to inject arbitrary HTML attribute keys and values, bypassing the auto escaping mechanism and potentially leading to XSS. It may also be possible to bypass attribute validation checks if they are blacklist-based.

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

The Jinja2 `xmlattr` filter improperly handles input, allowing injection of arbitrary HTML attribute keys and values into rendered templates. This bypasses Jinja2's auto-escaping mechanism, potentially enabling XSS attacks. Additionally, blacklist-based attribute validation can be circumvented.

MitigationUpgrade to a patched version of Jinja2. Alternatively, implement strict allowlist-based input validation on any user-controlled data passed to the `xmlattr` filter to prevent attribute injection.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JinjaApplication
Affected:< 3.1.3

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Find installed Jinja2 version
    Run `pip show jinja2` or check your dependency lock file for the Jinja2 version number
    Affected if The version is lower than 3.1.3 (compare your installed version to the affected ranges)
  2. Locate uses of the xmlattr filter
    Search your codebase (templates and Python files) for instances of the `| xmlattr` filter, for example in Jinja2 templates like `{{ data|xmlattr }}` or in code using `Environment().get_template().module.__dict__`
    Affected if The `xmlattr` filter is used in your templates or called in Python code
  3. Identify data passed to xmlattr
    Review all code paths where data is passed to the `xmlattr` filter - trace variables from view functions or API endpoints to the template filter usage
    Affected if User-controlled input (request parameters, API payloads, database values from external sources) flows directly into the `xmlattr` filter without prior validation
  4. Inspect rendered output for unexpected attributes
    Test the affected template endpoints with special characters in input (such as quotes, spaces, or `on*=` patterns like `onclick=`) and examine the HTML output for injected attributes
    Affected if The rendered HTML contains attribute keys or values that were not explicitly defined in your allowlist or expected input structure

You are affected if your Jinja2 version is below 3.1.3 AND the `xmlattr` filter is being used with user-supplied data without strict allowlist validation.

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.

dbcve · scoped
Upgrade available Upgrade to 3.1.3 or later
Fixed in 3.1.3
Interim mitigation

Upgrade to a patched version of Jinja2. Alternatively, implement strict allowlist-based input validation on any user-controlled data passed to the `xmlattr` filter to prevent attribute injection.

Recommended fix High confidence

Jinja 3.1.3

  1. 1. Check the currently installed Jinja version: pip show jinja2 or pip freeze | grep -i jinja
  2. 2. Upgrade Jinja to version 3.1.3 or later: pip install 'jinja2>=3.1.3'
  3. 3. Verify the upgrade was successful: pip show jinja2 (confirm version is 3.1.3 or higher)
  4. 4. Test all templates in your application that use the xmlattr filter to ensure correct rendering and that the XSS vulnerability is mitigated
  5. 5. If using a requirements.txt or Pipfile, update the Jinja2 dependency to specify version 3.1.3 or higher
Caveat Minor version upgrade focused on security fix; review custom template filters that interact with xmlattr

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jinja Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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