Description
Discourse is an open source platform for community discussion. This vulnerability only impacts Discourse instances configured to use `FileStore::LocalStore` which means uploads and backups are stored locally on disk. If an attacker knows the name of the Discourse backup file, the attacker can trick nginx into sending the Discourse backup file with a well crafted request. This issue is patched in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. Users unable to upgrade can either 1. Download all local backups on to another storage device, disable the `enable_backups` site setting and delete all backups until the site has been upgraded to pull in the fix. Or 2. Change the `backup_location` site setting to `s3` so that backups are stored and downloaded directly from S3.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| discourse | discourse | stable: <= 3.3.2, beta: <= 3.4.0.beta3, tests-passed: <= 3.4.0.beta3 | — |
Automated scanner template
A ready-made Nuclei template detects this vulnerability automatically. Vulnerabilities with public scanner templates are typically probed across the internet soon after the template appears — exposed systems should be patched first.
- Discourse Backup File Disclosure Via Default Nginx Configuration http/cves/2024/CVE-2024-53991.yaml
Source: projectdiscovery/nuclei-templates (MIT) — updated daily. Only links are listed.