CVE-2024-53991
moderateBackup file disclosure in Discourse instances using local disk storage
CVE-2024-53991 is an information exposure flaw (CWE-200) in Discourse, the open source community discussion platform, affecting only instances where uploads and backups are stored locally on disk via FileStore::LocalStore. An unauthenticated remote attacker who knows or can guess the name of the Discourse backup file can send a crafted request that tricks nginx into serving the backup file directly. Because backups typically contain a full dump of the site database, the attacker can gain potentially sensitive user data such as account records and site content. Only Discourse deployments using local backup storage are affected; the issue is fixed in the latest stable, beta, and tests-passed versions. No exploitation is confirmed, but EPSS assigns a relatively high 26.8% probability of exploitation within 30 days (98th percentile), with no public PoC and no CISA KEV listing.
What to do: Upgrade Discourse to the latest stable, beta, or tests-passed version, which contains the fix. If upgrading is not immediately possible, either download all local backups to separate storage, disable the enable_backups site setting, and delete backups until upgraded, or change the backup_location site setting to s3 so backups are stored and downloaded directly from S3. Administrators should confirm whether their instance uses local backup storage, since S3-backed and hosted instances are not affected.
| Discourse | Instances configured with FileStore::LocalStore (local on-disk backup storage); fixed in the latest stable, beta, and tests-passed versions at time of disclosur |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
- Vendors
- discourse
- Products
- discourse
- Weakness
- CWE-200
- Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
In the news0 stories
No ingested article mentions this CVE yet.