Skip to main content
VulnerabilityPublished Updated

CVE-2018-25111: django-helpdesk · Insecure Inherited Permissions

Affects django-helpdeskSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.0.0 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade django-helpdesk to 1.0.0.

Affected software

ProductAffectedFixed in
PyPIdjango-helpdeskpkg:pypi/django-helpdeskOther threatsAffected
  • <1.0.0
Fixed in
  • 1.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take the following specific steps to mitigate this vulnerability: 1) Upgrade django-helpdesk to version 1.0.0 or later where this issue is resolved. If an upgrade is not immediately possible, 2) Review and modify the source code to remove or alter the os.umask(0) call to enforce stricter file permission masks, such as os.umask(022), to prevent overly permissive file creation. 3) Audit file permissions on all files created by django-helpdesk to ensure they are not accessible by unauthorized users. 4) Restrict local system access to trusted users only, employing strong access controls and monitoring for unauthorized access attempts. 5) Implement file integrity monitoring on helpdesk data files to detect unauthorized modifications. 6) Conduct regular security training for administrators and users to recognize and prevent privilege escalation and insider threats. 7) Consider containerization or sandboxing of the django-helpdesk application to limit the impact of local exploits. These measures go beyond generic advice by focusing on the specific cause (os.umask misuse) and the operational context of django-helpdesk deployments.

Description

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

References

Community reviews

Loading reviews…