https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 20:51:46 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2003-0249 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://cve.radiocsirt.org/vuln/bell-cve-2003-0249 https://cve.radiocsirt.org/vuln/euvd-2026-175833 EUVD-2026-175833 https://cve.radiocsirt.org/vuln/euvd-2026-175833 https://cve.radiocsirt.org/vuln/fkie_cve-2003-0249 <p>PHP treats unknown methods such as &#34;PoSt&#34; as a GET request, which could allow attackers to intended access restrictions if PHP is running on a server that passes on all methods, such as Apache httpd 2.0, as demonstrated using a Limit directive. NOTE: this issue has been disputed by the Apache security team, saying &#34;It is by design that PHP allows scripts to process any request method. A script which does not explicitly verify the request method will hence be processed as normal for arbitrary methods. It is therefore expected behaviour that one cannot implement per-method access control using the Apache configuration alone, which is the assumption made in this report.</p> <p>PHP treats unknown methods such as &#34;PoSt&#34; as a GET request, which could allow attackers to intended access restrictions if PHP is running on a server that passes on all methods, such as Apache httpd 2.0, as demonstrated using a Limit directive. NOTE: this issue has been disputed by the Apache security team, saying &#34;It is by design that PHP allows scripts to process any request method. A script which does not explicitly verify the request method will hence be processed as normal for arbitrary methods. It is therefore expected behaviour that one cannot implement per-method access control using the Apache configuration alone, which is the assumption made in this report.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2003-0249 https://cve.radiocsirt.org/vuln/ghsa-xc5f-pfpm-hrw6 <p>** DISPUTED ** PHP treats unknown methods such as &#34;PoSt&#34; as a GET request, which could allow attackers to intended access restrictions if PHP is running on a server that passes on all methods, such as Apache httpd 2.0, as demonstrated using a Limit directive. NOTE: this issue has been disputed by the Apache security team, saying &#34;It is by design that PHP allows scripts to process any request method. A script which does not explicitly verify the request method will hence be processed as normal for arbitrary methods. It is therefore expected behaviour that one cannot implement per-method access control using the Apache configuration alone, which is the assumption made in this report.&#34;</p> <p>** DISPUTED ** PHP treats unknown methods such as &#34;PoSt&#34; as a GET request, which could allow attackers to intended access restrictions if PHP is running on a server that passes on all methods, such as Apache httpd 2.0, as demonstrated using a Limit directive. NOTE: this issue has been disputed by the Apache security team, saying &#34;It is by design that PHP allows scripts to process any request method. A script which does not explicitly verify the request method will hence be processed as normal for arbitrary methods. It is therefore expected behaviour that one cannot implement per-method access control using the Apache configuration alone, which is the assumption made in this report.&#34;</p> https://cve.radiocsirt.org/vuln/ghsa-xc5f-pfpm-hrw6 https://cve.radiocsirt.org/vuln/gsd-2003-0249 gsd-2003-0249 https://cve.radiocsirt.org/vuln/gsd-2003-0249