https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 21:46:55 +0000 https://cve.radiocsirt.org/vuln/cnvd-2021-19675 cnvd-2021-19675 https://cve.radiocsirt.org/vuln/cnvd-2021-19675 https://cve.radiocsirt.org/vuln/euvd-2026-241971 EUVD-2026-241971 https://cve.radiocsirt.org/vuln/euvd-2026-241971 https://cve.radiocsirt.org/vuln/fkie_cve-2021-21265 <p>October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October before version 1.1.2, when running on poorly configured servers (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. This has been addressed in version 1.1.2 by adding a feature to allow a set of trusted hosts to be specified in the application. As a workaround one may set the configuration setting cms.linkPolicy to force.</p> <p>October is a free, open-source, self-hosted CMS platform based on the Laravel PHP Framework. In October before version 1.1.2, when running on poorly configured servers (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. This has been addressed in version 1.1.2 by adding a feature to allow a set of trusted hosts to be specified in the application. As a workaround one may set the configuration setting cms.linkPolicy to force.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-21265 https://cve.radiocsirt.org/vuln/ghsa-xhfx-hgmf-v6vp <p><strong>Affected:</strong> Packagist: october/backend</p> <p>### Impact When running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning: - https://portswigger.net/web-security/host-header - https://dzone.com/articles/what-is-a-host-header-attack</p> <p>### Patches</p> <p>A feature has been added in v1.1.2 to allow a set of trusted hosts to be specified in the application.</p> <p>### Workarounds</p> <p>- Apply https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6 &amp; https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0 to your installation manually if unable to upgrade to v1.1.2.</p> <p>- Check that the configuration setting `cms.linkPolicy` is set to `force`.</p> <p>### Alternative Workaround</p> <p>Check to make sure that your web server does not accept any hostname when serving your web application.</p> <p>1. Add an entry called `testing.tld` to your computer&#39;s host file and direct it to your server&#39;s IP address 2. Open the address `testing.tld` in your web browser 3. Make sure an October CMS website is not available at this address</p> <p>If an October CMS website is returned, configure your webserver to only allow known hostnames. If you require assistance with this, please contact your server administrator.</p> <p>### References</p> <p>Reported by [Abdullah Hussam](https://github.com/ah…</p> <p><strong>Affected:</strong> Packagist: october/backend</p> <p>### Impact When running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning: - https://portswigger.net/web-security/host-header - https://dzone.com/articles/what-is-a-host-header-attack</p> <p>### Patches</p> <p>A feature has been added in v1.1.2 to allow a set of trusted hosts to be specified in the application.</p> <p>### Workarounds</p> <p>- Apply https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6 &amp; https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0 to your installation manually if unable to upgrade to v1.1.2.</p> <p>- Check that the configuration setting `cms.linkPolicy` is set to `force`.</p> <p>### Alternative Workaround</p> <p>Check to make sure that your web server does not accept any hostname when serving your web application.</p> <p>1. Add an entry called `testing.tld` to your computer&#39;s host file and direct it to your server&#39;s IP address 2. Open the address `testing.tld` in your web browser 3. Make sure an October CMS website is not available at this address</p> <p>If an October CMS website is returned, configure your webserver to only allow known hostnames. If you require assistance with this, please contact your server administrator.</p> <p>### References</p> <p>Reported by [Abdullah Hussam](https://github.com/ah…</p> https://cve.radiocsirt.org/vuln/ghsa-xhfx-hgmf-v6vp https://cve.radiocsirt.org/vuln/gsd-2021-21265 gsd-2021-21265 https://cve.radiocsirt.org/vuln/gsd-2021-21265