dbcve.org
Django MarkupfieldFramework / library · Django Markupfield Project

CVE-2015-0846

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-24
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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
django-markupfield before 1.3.2 uses the default docutils RESTRUCTUREDTEXT_FILTER_SETTINGS settings, which allows remote attackers to include and read arbitrary files via unspecified vectors.

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 django-markupfield library before version 1.3.2 uses default docutils RESTRUCTUREDTEXT_FILTER_SETTINGS that allow arbitrary file inclusion and reading through unspecified vectors in reStructuredText content processed by the markup field.

MitigationUpgrade django-markupfield to version 1.3.2 or later and explicitly configure RESTRUCTUREDTEXT_FILTER_SETTINGS to restrict file access patterns.

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
Django MarkupfieldFramework / library
Affected:<= 1.3.1

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 django-markupfield is installed
    Run 'pip show django-markupfield' or check your requirements.txt/environment for the django-markupfield package
    Affected if The package is present in the environment
  2. Determine the installed version
    Run 'pip show django-markupfield' and note the Version field, or check your installed packages list
    Affected if Version is 1.3.1 or earlier
  3. Locate markup field usage in Django models
    Search your Django project code for fields using markupfield MarkupField, typically found in models.py files with 'MarkupField' or 'markup=' parameters
    Affected if MarkupField is used in any model without explicit filter_settings configuration
  4. Check RESTRUCTUREDTEXT_FILTER_SETTINGS configuration
    Inspect your Django settings.py for RESTRUCTUREDTEXT_FILTER_SETTINGS - search for this exact setting name and review its value if present
    Affected if The setting is absent (uses library defaults) or contains permissive file access patterns

You are affected if django-markupfield version 1.3.1 or earlier is installed AND MarkupField is used with reStructuredText markup without explicit RESTRUCTUREDTEXT_FILTER_SETTINGS restrictions in settings.

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
Upgrade available Upgrade to a release after 1.3.1
Interim mitigation

Upgrade django-markupfield to version 1.3.2 or later and explicitly configure RESTRUCTUREDTEXT_FILTER_SETTINGS to restrict file access patterns.

Fix this in Django Markupfield Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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