# django-helpdesk before 1.0.0 allows Sensitive Data Exposure because of os.umask(0) in models.py.

Advisory record · `GHSA-m4jx-m5hg-qrxx`

- **Identifiers:** `GHSA-m4jx-m5hg-qrxx` · `CVE-2018-25111` · `PYSEC-2025-44`
- **State:** Confirmed
- **Severity:** CVSS 5.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-277](https://cwe.mitre.org/data/definitions/277.html)
- **Tags:** [CWE-277](https://agentprime.io/advisories/tag/cwe-277.md)
- **Published:** 31 May 2025
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 31 May 2025, 01:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django-helpdesk` (PyPI): affected `<0d91fcca0b6a98a4e7248368bc1dc4f06c682159 || <1.0.0`; fixed in `0d91fcca0b6a98a4e7248368bc1dc4f06c682159`, `1.0.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.1 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 11th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 31 May 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-m4jx-m5hg-qrxx](https://github.com/advisories/GHSA-m4jx-m5hg-qrxx)
- [OSV: GHSA-m4jx-m5hg-qrxx](https://osv.dev/vulnerability/GHSA-m4jx-m5hg-qrxx)
- <https://github.com/django-helpdesk/django-helpdesk/pull/1120>
- <https://github.com/django-helpdesk/django-helpdesk/releases/tag/v1.0.0>
- <https://github.com/advisories/GHSA-m4jx-m5hg-qrxx>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m4jx-m5hg-qrxx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m4jx-m5hg-qrxx/>. Everything for agents: <https://agentprime.io/llms.txt>.