# Security issues from automated scans

**URL:** <https://meta.discourse.org/t/security-issues-from-automated-scans/330948>\
**Category:** Support\
**Created:** [October 15, 2024, 10:33am UTC](https://meta.discourse.org/t/security-issues-from-automated-scans/330948 "2024-10-15T10:33:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)\
**Post date:** [October 15, 2024, 10:56am UTC](https://meta.discourse.org/t/security-issues-from-automated-scans/330948/3 "2024-10-15T10:56:06Z")

</div>

From [discourse/docs/SECURITY.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/docs/SECURITY.md)

> Where should I report security issues?
> 
> In order to give the community time to respond and upgrade we strongly urge you report all security issues privately. Please use our [vulnerability disclosure program at Hacker One](https://hackerone.com/discourse) to provide details and repro steps and we will respond ASAP. If you are unable to use Hacker One, email us directly at `team@discourse.org` with details and repro steps. Security issues _always_ take precedence over bug fixes and feature work. We can and do mark releases as “urgent” if they contain serious security fixes.
> 
> **Please note:** Due to a significant number of low quality security reports sent via email, we are unlikely to act on security reports sent to us via email unless they come from a trusted source, and include details on the vulnerability and step by step instructions to reproduce it. Theoretical reports without a proof of concept are not accepted. We strongly recommend you follow the Hacker One submission protocols.

---

_[View the full topic](https://meta.discourse.org/t/security-issues-from-automated-scans/330948)._