Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: https://waf-bypass.com/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>Web application firewalls bypasses collection and testing tools</title>
  12. <atom:link href="https://waf-bypass.com/feed/" rel="self" type="application/rss+xml" />
  13. <link>https://waf-bypass.com</link>
  14. <description>How to test, evaluate, compare, and bypass web application and API security solutions like WAF, NGWAF, RASP, and WAAP</description>
  15. <lastBuildDate>Fri, 18 Apr 2025 08:00:03 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.7.2</generator>
  22.  
  23. <image>
  24. <url>https://waf-bypass.com/wp-content/uploads/2021/11/cropped-favicon-1-1-32x32.png</url>
  25. <title>Web application firewalls bypasses collection and testing tools</title>
  26. <link>https://waf-bypass.com</link>
  27. <width>32</width>
  28. <height>32</height>
  29. </image>
  30. <item>
  31. <title>WAF bypass by mohammed97mus</title>
  32. <link>https://waf-bypass.com/2025/04/18/waf-bypass-by-mohammed97mus/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-mohammed97mus</link>
  33. <comments>https://waf-bypass.com/2025/04/18/waf-bypass-by-mohammed97mus/#respond</comments>
  35. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  36. <pubDate>Fri, 18 Apr 2025 08:00:03 +0000</pubDate>
  37. <category><![CDATA[Uncategorized]]></category>
  38. <guid isPermaLink="false">http://waf-bypass.com/2025/04/18/waf-bypass-by-mohammed97mus/</guid>
  39.  
  40. <description><![CDATA[To hunt for SSRF WAF bypass, you can start by analyzing the target application for potential SSRF vulnerabilities. Look for user-controlled input that interacts with external resources. Test different protocols like HTTP, FTP, and file:// to see if the WAF allows SSRF attacks. Try variations in the URLs and observe WAF responses. Additionally, research bypass [&#8230;]]]></description>
  41. <content:encoded><![CDATA[<p>To hunt for SSRF WAF bypass, you can start by analyzing the target application for potential SSRF vulnerabilities. Look for user-controlled input that interacts with external resources. Test different protocols like HTTP, FTP, and file:// to see if the WAF allows SSRF attacks. Try variations in the URLs and observe WAF responses. Additionally, research bypass techniques specific to the WAF in use. Remember to perform these tests responsibly and with permission.</p>
  42. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  43. <p lang="en" dir="ltr">please how to hunt for ssrf waf bypass</p>
  44. <p>&mdash; mohammed ameer (@mohammed97mus) <a href="https://twitter.com/mohammed97mus/status/1912849345755349016?ref_src=twsrc%5Etfw">April 17, 2025</a></p></blockquote>
  45. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  46. ]]></content:encoded>
  48. <wfw:commentRss>https://waf-bypass.com/2025/04/18/waf-bypass-by-mohammed97mus/feed/</wfw:commentRss>
  49. <slash:comments>0</slash:comments>
  52. </item>
  53. <item>
  54. <title>WAF bypass by MiniMjStar</title>
  55. <link>https://waf-bypass.com/2025/04/18/waf-bypass-by-minimjstar-16/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-minimjstar-16</link>
  56. <comments>https://waf-bypass.com/2025/04/18/waf-bypass-by-minimjstar-16/#respond</comments>
  58. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  59. <pubDate>Fri, 18 Apr 2025 07:00:03 +0000</pubDate>
  60. <category><![CDATA[Uncategorized]]></category>
  61. <guid isPermaLink="false">http://waf-bypass.com/2025/04/18/waf-bypass-by-minimjstar-16/</guid>
  62.  
  63. <description><![CDATA[This tweet discusses bypassing source check on postMessage to achieve XSS. It highlights a method to bypass security checks in order to execute a cross-site scripting attack. This vulnerability can potentially affect various WAF vendors. For more technical details, please refer to the original tweet by @elmehdimee. For more insights, check out the original tweet [&#8230;]]]></description>
  64. <content:encoded><![CDATA[<p>This tweet discusses bypassing source check on postMessage to achieve XSS. It highlights a method to bypass security checks in order to execute a cross-site scripting attack. This vulnerability can potentially affect various WAF vendors. For more technical details, please refer to the original tweet by @elmehdimee.<br />
  65. For more insights, check out the original tweet here: https://twitter.com/MiniMjStar/status/1912942937043796142</p>
  66. ]]></content:encoded>
  68. <wfw:commentRss>https://waf-bypass.com/2025/04/18/waf-bypass-by-minimjstar-16/feed/</wfw:commentRss>
  69. <slash:comments>0</slash:comments>
  72. </item>
  73. <item>
  74. <title>WAF bypass by xn0kkx</title>
  75. <link>https://waf-bypass.com/2025/04/18/waf-bypass-by-xn0kkx/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-xn0kkx</link>
  76. <comments>https://waf-bypass.com/2025/04/18/waf-bypass-by-xn0kkx/#respond</comments>
  78. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  79. <pubDate>Fri, 18 Apr 2025 06:00:03 +0000</pubDate>
  80. <category><![CDATA[Uncategorized]]></category>
  81. <guid isPermaLink="false">http://waf-bypass.com/2025/04/18/waf-bypass-by-xn0kkx/</guid>
  82.  
  83. <description><![CDATA[This tweet discusses SQL injection as a vulnerability that requires knowledge of SQL. It mentions that the WAF blocks payloads, so bypass techniques need to be used. For more insights, check out the original tweet here: https://twitter.com/xn0kkx/status/1913040481488888003. And don’t forget to follow @xn0kkx for more exciting updates in the world of cybersecurity.]]></description>
  84. <content:encoded><![CDATA[<p>This tweet discusses SQL injection as a vulnerability that requires knowledge of SQL. It mentions that the WAF blocks payloads, so bypass techniques need to be used.<br />
  85. For more insights, check out the original tweet here: https://twitter.com/xn0kkx/status/1913040481488888003. And don’t forget to follow @xn0kkx for more exciting updates in the world of cybersecurity.</p>
  86. ]]></content:encoded>
  88. <wfw:commentRss>https://waf-bypass.com/2025/04/18/waf-bypass-by-xn0kkx/feed/</wfw:commentRss>
  89. <slash:comments>0</slash:comments>
  92. </item>
  93. <item>
  94. <title>WAF bypass by ssdd934</title>
  95. <link>https://waf-bypass.com/2025/04/18/waf-bypass-by-ssdd934/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-ssdd934</link>
  96. <comments>https://waf-bypass.com/2025/04/18/waf-bypass-by-ssdd934/#respond</comments>
  98. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  99. <pubDate>Fri, 18 Apr 2025 05:00:02 +0000</pubDate>
  100. <category><![CDATA[Uncategorized]]></category>
  101. <guid isPermaLink="false">http://waf-bypass.com/2025/04/18/waf-bypass-by-ssdd934/</guid>
  102.  
  103. <description><![CDATA[The tweet mentions finding a vulnerable endpoint multiple times, but the payload being blocked by the WAF. It highlights the challenge of bypassing the WAF protection. Further details about the specific WAF vendor and bypass payload are not provided. Check out the original tweet here: https://twitter.com/ssdd934/status/1913049239229182227]]></description>
  104. <content:encoded><![CDATA[<p>The tweet mentions finding a vulnerable endpoint multiple times, but the payload being blocked by the WAF. It highlights the challenge of bypassing the WAF protection. Further details about the specific WAF vendor and bypass payload are not provided.<br />
  105. Check out the original tweet here: https://twitter.com/ssdd934/status/1913049239229182227</p>
  106. ]]></content:encoded>
  108. <wfw:commentRss>https://waf-bypass.com/2025/04/18/waf-bypass-by-ssdd934/feed/</wfw:commentRss>
  109. <slash:comments>0</slash:comments>
  112. </item>
  113. <item>
  114. <title>WAF bypass by coffinxp7</title>
  115. <link>https://waf-bypass.com/2025/04/17/waf-bypass-by-coffinxp7-40/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-coffinxp7-40</link>
  116. <comments>https://waf-bypass.com/2025/04/17/waf-bypass-by-coffinxp7-40/#respond</comments>
  118. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  119. <pubDate>Thu, 17 Apr 2025 07:00:02 +0000</pubDate>
  120. <category><![CDATA[Uncategorized]]></category>
  121. <guid isPermaLink="false">http://waf-bypass.com/2025/04/17/waf-bypass-by-coffinxp7-40/</guid>
  122.  
  123. <description><![CDATA[The tweet demonstrates real-time bypasses of Cloudflare and ModSecurity using ProxyChains + tamper scripts for SQL Injection. It can be helpful for users looking to level up their WAF bypass knowledge. For more technical details, visit the link provided in the tweet. The WAF Bypass video is finally live!I demonstrated real-time bypasses of Cloudflare and [&#8230;]]]></description>
  124. <content:encoded><![CDATA[<p>The tweet demonstrates real-time bypasses of Cloudflare and ModSecurity using ProxyChains + tamper scripts for SQL Injection. It can be helpful for users looking to level up their WAF bypass knowledge. For more technical details, visit the link provided in the tweet.</p>
  125. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  126. <p lang="en" dir="ltr">The WAF Bypass video is finally live!<br />I demonstrated real-time bypasses of Cloudflare and ModSecurity using ProxyChains + tamper scripts+ mass hunting SQL injection..Hope it helps you level up!<a href="https://t.co/rdfdf5mHEQ">https://t.co/rdfdf5mHEQ</a></p>
  127. <p>&mdash; Coffin (@coffinxp7) <a href="https://twitter.com/coffinxp7/status/1912397335901962562?ref_src=twsrc%5Etfw">April 16, 2025</a></p></blockquote>
  128. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  129. ]]></content:encoded>
  131. <wfw:commentRss>https://waf-bypass.com/2025/04/17/waf-bypass-by-coffinxp7-40/feed/</wfw:commentRss>
  132. <slash:comments>0</slash:comments>
  135. </item>
  136. <item>
  137. <title>WAF bypass by 40sp3l</title>
  138. <link>https://waf-bypass.com/2025/04/17/waf-bypass-by-40sp3l-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-40sp3l-2</link>
  139. <comments>https://waf-bypass.com/2025/04/17/waf-bypass-by-40sp3l-2/#respond</comments>
  141. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  142. <pubDate>Thu, 17 Apr 2025 06:00:02 +0000</pubDate>
  143. <category><![CDATA[Uncategorized]]></category>
  144. <guid isPermaLink="false">http://waf-bypass.com/2025/04/17/waf-bypass-by-40sp3l-2/</guid>
  145.  
  146. <description><![CDATA[A WAF bypass technique using Sqlmap, Proxychain, and Tamper Scripts to bypass Cloudflare and Modsecurity WAF. This technique allows attackers to exploit SQL Injection vulnerabilities effectively. For more technical details, refer to the tweet: https://t.co/08cvo9PR9v Check out the original tweet here: https://twitter.com/40sp3l/status/1912699084340670862]]></description>
  147. <content:encoded><![CDATA[<p>A WAF bypass technique using Sqlmap, Proxychain, and Tamper Scripts to bypass Cloudflare and Modsecurity WAF. This technique allows attackers to exploit SQL Injection vulnerabilities effectively. For more technical details, refer to the tweet: https://t.co/08cvo9PR9v<br />
  148. Check out the original tweet here: https://twitter.com/40sp3l/status/1912699084340670862</p>
  149. ]]></content:encoded>
  151. <wfw:commentRss>https://waf-bypass.com/2025/04/17/waf-bypass-by-40sp3l-2/feed/</wfw:commentRss>
  152. <slash:comments>0</slash:comments>
  155. </item>
  156. <item>
  157. <title>WAF bypass by XssPayloads</title>
  158. <link>https://waf-bypass.com/2025/04/17/waf-bypass-by-xsspayloads-23/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-xsspayloads-23</link>
  159. <comments>https://waf-bypass.com/2025/04/17/waf-bypass-by-xsspayloads-23/#respond</comments>
  161. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  162. <pubDate>Thu, 17 Apr 2025 05:00:02 +0000</pubDate>
  163. <category><![CDATA[Uncategorized]]></category>
  164. <guid isPermaLink="false">http://waf-bypass.com/2025/04/17/waf-bypass-by-xsspayloads-23/</guid>
  165.  
  166. <description><![CDATA[A XSS payload in JS context was discovered by @thelilnix for WAF bypass. The payload used is &#039;&#039;.replace.call`1${/&#8230;/}${alert}`. This bypass can affect various WAF vendors. It is recommended to apply appropriate security measures to prevent such bypasses. A XSS payload in JS context for WAF bypass, by @thelilnix &#39;&#39;.replace.call`1${/&#8230;/}${alert}` &#8212; XSS Payloads (@XssPayloads) April 17, [&#8230;]]]></description>
  167. <content:encoded><![CDATA[<p>A XSS payload in JS context was discovered by @thelilnix for WAF bypass. The payload used is &#039;&#039;.replace.call`1${/&#8230;/}${alert}`. This bypass can affect various WAF vendors. It is recommended to apply appropriate security measures to prevent such bypasses.</p>
  168. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  169. <p lang="en" dir="ltr">A XSS payload in JS context for WAF bypass, by <a href="https://twitter.com/thelilnix?ref_src=twsrc%5Etfw">@thelilnix</a></p>
  170. <p>&#39;&#39;.replace.call`1${/&#8230;/}${alert}`</p>
  171. <p>&mdash; XSS Payloads (@XssPayloads) <a href="https://twitter.com/XssPayloads/status/1912703059110613115?ref_src=twsrc%5Etfw">April 17, 2025</a></p></blockquote>
  172. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  173. ]]></content:encoded>
  175. <wfw:commentRss>https://waf-bypass.com/2025/04/17/waf-bypass-by-xsspayloads-23/feed/</wfw:commentRss>
  176. <slash:comments>0</slash:comments>
  179. </item>
  180. <item>
  181. <title>WAF bypass by coffinxp7</title>
  182. <link>https://waf-bypass.com/2025/04/16/waf-bypass-by-coffinxp7-39/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-coffinxp7-39</link>
  183. <comments>https://waf-bypass.com/2025/04/16/waf-bypass-by-coffinxp7-39/#respond</comments>
  185. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  186. <pubDate>Wed, 16 Apr 2025 10:00:03 +0000</pubDate>
  187. <category><![CDATA[Uncategorized]]></category>
  188. <guid isPermaLink="false">http://waf-bypass.com/2025/04/16/waf-bypass-by-coffinxp7-39/</guid>
  189.  
  190. <description><![CDATA[The tweet mentions working on a WAF bypass video using proxychains. Proxychains is a tool used for proxying connections through different proxies. The tweet lacks specific details about the vulnerability type and WAF vendor. It would be helpful to provide more information in the future to better understand the context of the bypass. For more [&#8230;]]]></description>
  191. <content:encoded><![CDATA[<p>The tweet mentions working on a WAF bypass video using proxychains. Proxychains is a tool used for proxying connections through different proxies. The tweet lacks specific details about the vulnerability type and WAF vendor. It would be helpful to provide more information in the future to better understand the context of the bypass.<br />
  192. For more details, check out the original tweet here: https://twitter.com/coffinxp7/status/1912143440806130105</p>
  193. ]]></content:encoded>
  195. <wfw:commentRss>https://waf-bypass.com/2025/04/16/waf-bypass-by-coffinxp7-39/feed/</wfw:commentRss>
  196. <slash:comments>0</slash:comments>
  199. </item>
  200. <item>
  201. <title>WAF bypass by thelilnix</title>
  202. <link>https://waf-bypass.com/2025/04/16/waf-bypass-by-thelilnix-3/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-thelilnix-3</link>
  203. <comments>https://waf-bypass.com/2025/04/16/waf-bypass-by-thelilnix-3/#respond</comments>
  205. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  206. <pubDate>Wed, 16 Apr 2025 09:00:04 +0000</pubDate>
  207. <category><![CDATA[Uncategorized]]></category>
  208. <guid isPermaLink="false">http://waf-bypass.com/2025/04/16/waf-bypass-by-thelilnix-3/</guid>
  209.  
  210. <description><![CDATA[This XSS payload utilizes the replace method in JavaScript to bypass WAF protection. The payload inserts a malicious alert function within the context, which can execute arbitrary JavaScript code. This bypass technique is inspired by the &#039;JavaScript for Hackers&#039; book by @garethheyes. It is important for WAF vendors to be aware of such evasion techniques [&#8230;]]]></description>
  211. <content:encoded><![CDATA[<p>This XSS payload utilizes the replace method in JavaScript to bypass WAF protection. The payload inserts a malicious alert function within the context, which can execute arbitrary JavaScript code. This bypass technique is inspired by the &#039;JavaScript for Hackers&#039; book by @garethheyes. It is important for WAF vendors to be aware of such evasion techniques to enhance their security measures.<br />
  212. For more details, check out the original tweet here: https://twitter.com/thelilnix/status/1912185244997787998</p>
  213. ]]></content:encoded>
  215. <wfw:commentRss>https://waf-bypass.com/2025/04/16/waf-bypass-by-thelilnix-3/feed/</wfw:commentRss>
  216. <slash:comments>0</slash:comments>
  219. </item>
  220. <item>
  221. <title>WAF bypass by hackervirus999</title>
  222. <link>https://waf-bypass.com/2025/04/16/waf-bypass-by-hackervirus999/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-hackervirus999</link>
  223. <comments>https://waf-bypass.com/2025/04/16/waf-bypass-by-hackervirus999/#respond</comments>
  225. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  226. <pubDate>Wed, 16 Apr 2025 08:00:03 +0000</pubDate>
  227. <category><![CDATA[Uncategorized]]></category>
  228. <guid isPermaLink="false">http://waf-bypass.com/2025/04/16/waf-bypass-by-hackervirus999/</guid>
  229.  
  230. <description><![CDATA[A bypass was discovered in Cloudflare WAF that allows for Origin IP Leakage. This vulnerability can potentially expose the IP address of the origin server behind the WAF. More details should be investigated and addressed by Cloudflare to mitigate this issue. Original tweet: https://twitter.com/hackervirus999/status/1912203682680029679]]></description>
  231. <content:encoded><![CDATA[<p>A bypass was discovered in Cloudflare WAF that allows for Origin IP Leakage. This vulnerability can potentially expose the IP address of the origin server behind the WAF. More details should be investigated and addressed by Cloudflare to mitigate this issue.<br />
  232. Original tweet: https://twitter.com/hackervirus999/status/1912203682680029679</p>
  233. ]]></content:encoded>
  235. <wfw:commentRss>https://waf-bypass.com/2025/04/16/waf-bypass-by-hackervirus999/feed/</wfw:commentRss>
  236. <slash:comments>0</slash:comments>
  239. </item>
  240. <item>
  241. <title>WAF bypass by issa0601</title>
  242. <link>https://waf-bypass.com/2025/04/16/waf-bypass-by-issa0601/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-issa0601</link>
  243. <comments>https://waf-bypass.com/2025/04/16/waf-bypass-by-issa0601/#respond</comments>
  245. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  246. <pubDate>Wed, 16 Apr 2025 07:00:03 +0000</pubDate>
  247. <category><![CDATA[Uncategorized]]></category>
  248. <guid isPermaLink="false">http://waf-bypass.com/2025/04/16/waf-bypass-by-issa0601/</guid>
  249.  
  250. <description><![CDATA[The tweet mentions creating a payload for a WAF bypass. It indicates that the user cannot sleep and is preparing a payload to try a WAF bypass tomorrow. Since the specific vulnerability type and WAF vendor are not mentioned, further details are needed to analyze this bypass effectively. ????????????????WAF bypass??????????? &#8212; ISSA (@issa0601) April 15, [&#8230;]]]></description>
  251. <content:encoded><![CDATA[<p>The tweet mentions creating a payload for a WAF bypass. It indicates that the user cannot sleep and is preparing a payload to try a WAF bypass tomorrow. Since the specific vulnerability type and WAF vendor are not mentioned, further details are needed to analyze this bypass effectively.</p>
  252. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  253. <p lang="ja" dir="ltr">????????????????WAF bypass<br />???????????</p>
  254. <p>&mdash; ISSA (@issa0601) <a href="https://twitter.com/issa0601/status/1912226872504848468?ref_src=twsrc%5Etfw">April 15, 2025</a></p></blockquote>
  255. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  256. ]]></content:encoded>
  258. <wfw:commentRss>https://waf-bypass.com/2025/04/16/waf-bypass-by-issa0601/feed/</wfw:commentRss>
  259. <slash:comments>0</slash:comments>
  262. </item>
  263. <item>
  264. <title>WAF bypass by iototsecnews</title>
  265. <link>https://waf-bypass.com/2025/04/16/waf-bypass-by-iototsecnews-3/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-iototsecnews-3</link>
  266. <comments>https://waf-bypass.com/2025/04/16/waf-bypass-by-iototsecnews-3/#respond</comments>
  268. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  269. <pubDate>Wed, 16 Apr 2025 06:00:03 +0000</pubDate>
  270. <category><![CDATA[Uncategorized]]></category>
  271. <guid isPermaLink="false">http://waf-bypass.com/2025/04/16/waf-bypass-by-iototsecnews-3/</guid>
  272.  
  273. <description><![CDATA[A vulnerability CVE-2025-31137 has been discovered in React Router, a library providing routing functionality. This vulnerability poses risks such as web app cache pollution and WAF bypass. By manipulating headers, attackers can exploit this vulnerability to bypass WAF protection. More details and technical information can be found in the provided link: https://t.co/RGsM1CU0YV React Router ? [&#8230;]]]></description>
  274. <content:encoded><![CDATA[<p>A vulnerability CVE-2025-31137 has been discovered in React Router, a library providing routing functionality. This vulnerability poses risks such as web app cache pollution and WAF bypass. By manipulating headers, attackers can exploit this vulnerability to bypass WAF protection. More details and technical information can be found in the provided link: https://t.co/RGsM1CU0YV</p>
  275. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  276. <p lang="ja" dir="ltr">React Router ? CVE-2025-31137 ? FIX?Web App ???????? WAF ?????????<a href="https://t.co/RGsM1CU0YV">https://t.co/RGsM1CU0YV</a><br />?????????????????? React Router ???????????????????????????????????? WAF…</p>
  277. <p>&mdash; iototsecnews (@iototsecnews) <a href="https://twitter.com/iototsecnews/status/1912308105901404643?ref_src=twsrc%5Etfw">April 16, 2025</a></p></blockquote>
  278. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  279. ]]></content:encoded>
  281. <wfw:commentRss>https://waf-bypass.com/2025/04/16/waf-bypass-by-iototsecnews-3/feed/</wfw:commentRss>
  282. <slash:comments>0</slash:comments>
  285. </item>
  286. <item>
  287. <title>WAF bypass by Syynya</title>
  288. <link>https://waf-bypass.com/2025/04/16/waf-bypass-by-syynya/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-syynya</link>
  289. <comments>https://waf-bypass.com/2025/04/16/waf-bypass-by-syynya/#respond</comments>
  291. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  292. <pubDate>Wed, 16 Apr 2025 05:00:03 +0000</pubDate>
  293. <category><![CDATA[Uncategorized]]></category>
  294. <guid isPermaLink="false">http://waf-bypass.com/2025/04/16/waf-bypass-by-syynya/</guid>
  295.  
  296. <description><![CDATA[A vulnerability (CVE-2025-31137) affecting React Router has been fixed to prevent Web App Cache Pollution and WAF bypass. Detailed technical information about the bypass can be found in the blog post at @iototsecnews. Check out the original tweet here: https://twitter.com/Syynya/status/1912355075772825789]]></description>
  297. <content:encoded><![CDATA[<p>A vulnerability (CVE-2025-31137) affecting React Router has been fixed to prevent Web App Cache Pollution and WAF bypass. Detailed technical information about the bypass can be found in the blog post at @iototsecnews.<br />
  298. Check out the original tweet here: https://twitter.com/Syynya/status/1912355075772825789</p>
  299. ]]></content:encoded>
  301. <wfw:commentRss>https://waf-bypass.com/2025/04/16/waf-bypass-by-syynya/feed/</wfw:commentRss>
  302. <slash:comments>0</slash:comments>
  305. </item>
  306. <item>
  307. <title>WAF bypass by Numero_Hacks</title>
  308. <link>https://waf-bypass.com/2025/04/15/waf-bypass-by-numero_hacks/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-numero_hacks</link>
  309. <comments>https://waf-bypass.com/2025/04/15/waf-bypass-by-numero_hacks/#respond</comments>
  311. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  312. <pubDate>Tue, 15 Apr 2025 06:00:02 +0000</pubDate>
  313. <category><![CDATA[Uncategorized]]></category>
  314. <guid isPermaLink="false">http://waf-bypass.com/2025/04/15/waf-bypass-by-numero_hacks/</guid>
  315.  
  316. <description><![CDATA[A stored XSS vulnerability was discovered on a private bug bounty program at HackerOne. The bypass payload used was &#60;Img Src=OnXSS OnError=confirm(&#34;Hacked_by_a7madn1&#34;)&#62;. This payload executed a confirm message &#039;Hacked_by_a7madn1&#039;. For more details, read the Write-Up at #bugbountytips #xss #Hacked: https://t.co/vfr5AX4GnF Original tweet: https://twitter.com/Numero_Hacks/status/1911715279400231014]]></description>
  317. <content:encoded><![CDATA[<p>A stored XSS vulnerability was discovered on a private bug bounty program at HackerOne. The bypass payload used was &lt;Img Src=OnXSS OnError=confirm(&quot;Hacked_by_a7madn1&quot;)&gt;. This payload executed a confirm message &#039;Hacked_by_a7madn1&#039;. For more details, read the Write-Up at #bugbountytips #xss #Hacked: https://t.co/vfr5AX4GnF<br />
  318. Original tweet: https://twitter.com/Numero_Hacks/status/1911715279400231014</p>
  319. ]]></content:encoded>
  321. <wfw:commentRss>https://waf-bypass.com/2025/04/15/waf-bypass-by-numero_hacks/feed/</wfw:commentRss>
  322. <slash:comments>0</slash:comments>
  325. </item>
  326. <item>
  327. <title>WAF bypass by nizarhammadi81</title>
  328. <link>https://waf-bypass.com/2025/04/15/waf-bypass-by-nizarhammadi81/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-nizarhammadi81</link>
  329. <comments>https://waf-bypass.com/2025/04/15/waf-bypass-by-nizarhammadi81/#respond</comments>
  331. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  332. <pubDate>Tue, 15 Apr 2025 05:00:02 +0000</pubDate>
  333. <category><![CDATA[Uncategorized]]></category>
  334. <guid isPermaLink="false">http://waf-bypass.com/2025/04/15/waf-bypass-by-nizarhammadi81/</guid>
  335.  
  336. <description><![CDATA[The tweet discusses a WAF Bypass Generator that helps hackers bypass WAFs using XSS, SQLi, and SSRF. This tool provides filtered payloads and bypass tricks tailored to known WAFs like Cloudflare, Akamai, etc. The generator assists in testing the effectiveness of WAFs against these common vulnerabilities. Detailed technical information and code examples related to this [&#8230;]]]></description>
  337. <content:encoded><![CDATA[<p>The tweet discusses a WAF Bypass Generator that helps hackers bypass WAFs using XSS, SQLi, and SSRF. This tool provides filtered payloads and bypass tricks tailored to known WAFs like Cloudflare, Akamai, etc. The generator assists in testing the effectiveness of WAFs against these common vulnerabilities. Detailed technical information and code examples related to this tool can be found in the blog post associated with this tweet.<br />
  338. Check out the original tweet here: https://twitter.com/nizarhammadi81/status/1911826921970942282</p>
  339. ]]></content:encoded>
  341. <wfw:commentRss>https://waf-bypass.com/2025/04/15/waf-bypass-by-nizarhammadi81/feed/</wfw:commentRss>
  342. <slash:comments>0</slash:comments>
  345. </item>
  346. <item>
  347. <title>WAF bypass by 40sp3l</title>
  348. <link>https://waf-bypass.com/2025/04/14/waf-bypass-by-40sp3l/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-40sp3l</link>
  349. <comments>https://waf-bypass.com/2025/04/14/waf-bypass-by-40sp3l/#respond</comments>
  351. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  352. <pubDate>Mon, 14 Apr 2025 05:00:03 +0000</pubDate>
  353. <category><![CDATA[Uncategorized]]></category>
  354. <guid isPermaLink="false">http://waf-bypass.com/2025/04/14/waf-bypass-by-40sp3l/</guid>
  355.  
  356. <description><![CDATA[This tweet mentions a tricky WAF bypass for reflected XSS. Unfortunately, no specific vendor is mentioned. It would be helpful to provide more technical details in order to analyze and understand the bypass better. For more insights, check out the original tweet here: https://twitter.com/40sp3l/status/1911482974199029784]]></description>
  357. <content:encoded><![CDATA[<p>This tweet mentions a tricky WAF bypass for reflected XSS. Unfortunately, no specific vendor is mentioned. It would be helpful to provide more technical details in order to analyze and understand the bypass better.<br />
  358. For more insights, check out the original tweet here: https://twitter.com/40sp3l/status/1911482974199029784</p>
  359. ]]></content:encoded>
  361. <wfw:commentRss>https://waf-bypass.com/2025/04/14/waf-bypass-by-40sp3l/feed/</wfw:commentRss>
  362. <slash:comments>0</slash:comments>
  365. </item>
  366. <item>
  367. <title>WAF bypass by HackingTeam777</title>
  368. <link>https://waf-bypass.com/2025/04/13/waf-bypass-by-hackingteam777-11/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-hackingteam777-11</link>
  369. <comments>https://waf-bypass.com/2025/04/13/waf-bypass-by-hackingteam777-11/#respond</comments>
  371. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  372. <pubDate>Sun, 13 Apr 2025 06:00:03 +0000</pubDate>
  373. <category><![CDATA[Uncategorized]]></category>
  374. <guid isPermaLink="false">http://waf-bypass.com/2025/04/13/waf-bypass-by-hackingteam777-11/</guid>
  375.  
  376. <description><![CDATA[This tweet showcases various techniques for bypassing WAF using commands such as &#039;cat&#039;, &#039;rev&#039;, &#039;od&#039;, &#039;tr&#039;, &#039;grep&#039;, &#039;cut&#039;, and &#039;paste&#039; on the &#039;/etc/hosts&#039; file. These commands are designed to trigger the WAF and potentially bypass its protection mechanisms. It is important for WAF administrators to be aware of these tactics to enhance their security measures. [&#8230;]]]></description>
  377. <content:encoded><![CDATA[<p>This tweet showcases various techniques for bypassing WAF using commands such as &#039;cat&#039;, &#039;rev&#039;, &#039;od&#039;, &#039;tr&#039;, &#039;grep&#039;, &#039;cut&#039;, and &#039;paste&#039; on the &#039;/etc/hosts&#039; file. These commands are designed to trigger the WAF and potentially bypass its protection mechanisms. It is important for WAF administrators to be aware of these tactics to enhance their security measures. Further analysis and testing are recommended to understand the full impact of these bypass techniques.<br />
  378. For more details, check out the original tweet here: https://twitter.com/HackingTeam777/status/1910939447908037114</p>
  379. ]]></content:encoded>
  381. <wfw:commentRss>https://waf-bypass.com/2025/04/13/waf-bypass-by-hackingteam777-11/feed/</wfw:commentRss>
  382. <slash:comments>0</slash:comments>
  385. </item>
  386. <item>
  387. <title>WAF bypass by galmanus</title>
  388. <link>https://waf-bypass.com/2025/04/13/waf-bypass-by-galmanus/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-galmanus</link>
  389. <comments>https://waf-bypass.com/2025/04/13/waf-bypass-by-galmanus/#respond</comments>
  391. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  392. <pubDate>Sun, 13 Apr 2025 05:00:02 +0000</pubDate>
  393. <category><![CDATA[Uncategorized]]></category>
  394. <guid isPermaLink="false">http://waf-bypass.com/2025/04/13/waf-bypass-by-galmanus/</guid>
  395.  
  396. <description><![CDATA[The tweet describes a successful XSS bypass on Cloudflare&#039;s WAF using encoded JS trickery. This bypass showcases the ability to evade Cloudflare&#039;s defense mechanisms with sophisticated payloads. It challenges others to share their next-level evasion techniques. Cloudflare users should be aware of the potential vulnerabilities and implement additional security measures to prevent XSS attacks. For [&#8230;]]]></description>
  397. <content:encoded><![CDATA[<p>The tweet describes a successful XSS bypass on Cloudflare&#039;s WAF using encoded JS trickery. This bypass showcases the ability to evade Cloudflare&#039;s defense mechanisms with sophisticated payloads. It challenges others to share their next-level evasion techniques. Cloudflare users should be aware of the potential vulnerabilities and implement additional security measures to prevent XSS attacks. For more details, visit our blogpost on this Cloudflare XSS bypass.<br />
  398. Check out the original tweet here: https://twitter.com/galmanus/status/1911005251433357480</p>
  399. ]]></content:encoded>
  401. <wfw:commentRss>https://waf-bypass.com/2025/04/13/waf-bypass-by-galmanus/feed/</wfw:commentRss>
  402. <slash:comments>0</slash:comments>
  405. </item>
  406. <item>
  407. <title>WAF bypass by Bensonhackz7</title>
  408. <link>https://waf-bypass.com/2025/04/12/waf-bypass-by-bensonhackz7/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-bensonhackz7</link>
  409. <comments>https://waf-bypass.com/2025/04/12/waf-bypass-by-bensonhackz7/#respond</comments>
  411. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  412. <pubDate>Sat, 12 Apr 2025 08:00:02 +0000</pubDate>
  413. <category><![CDATA[Uncategorized]]></category>
  414. <guid isPermaLink="false">http://waf-bypass.com/2025/04/12/waf-bypass-by-bensonhackz7/</guid>
  415.  
  416. <description><![CDATA[A stored XSS vulnerability was found on a private bug bounty program on HackerOne. The bypass payload used was &#039;&#60;Img Src=OnXSS OnError=confirm(&#34;Hacked_by_a7madn1&#34;)&#62;&#039;. This bypass affected a generic WAF. For more details, read the write-up at the provided link. #bugbountytips #xss #Hacked For more insights, check out the original tweet here: https://twitter.com/Bensonhackz7/status/1910595956510249367]]></description>
  417. <content:encoded><![CDATA[<p>A stored XSS vulnerability was found on a private bug bounty program on HackerOne. The bypass payload used was &#039;&lt;Img Src=OnXSS OnError=confirm(&quot;Hacked_by_a7madn1&quot;)&gt;&#039;. This bypass affected a generic WAF. For more details, read the write-up at the provided link. #bugbountytips #xss #Hacked<br />
  418. For more insights, check out the original tweet here: https://twitter.com/Bensonhackz7/status/1910595956510249367</p>
  419. ]]></content:encoded>
  421. <wfw:commentRss>https://waf-bypass.com/2025/04/12/waf-bypass-by-bensonhackz7/feed/</wfw:commentRss>
  422. <slash:comments>0</slash:comments>
  425. </item>
  426. <item>
  427. <title>WAF bypass by Ah5495811483065</title>
  428. <link>https://waf-bypass.com/2025/04/12/waf-bypass-by-ah5495811483065-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-ah5495811483065-2</link>
  429. <comments>https://waf-bypass.com/2025/04/12/waf-bypass-by-ah5495811483065-2/#respond</comments>
  431. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  432. <pubDate>Sat, 12 Apr 2025 07:00:03 +0000</pubDate>
  433. <category><![CDATA[Uncategorized]]></category>
  434. <guid isPermaLink="false">http://waf-bypass.com/2025/04/12/waf-bypass-by-ah5495811483065-2/</guid>
  435.  
  436. <description><![CDATA[The tweet mentions using open source tools for project discovery and utilizing AI for detecting vulnerabilities, specifically WAF bypass. It highlights two payloads for XSS and four for SQL injection, including the Xss0r with a worldlist of 5000 payloads for bypassing. The user expresses frustration about wasting money on the SmartScanner tool. A blog post [&#8230;]]]></description>
  437. <content:encoded><![CDATA[<p>The tweet mentions using open source tools for project discovery and utilizing AI for detecting vulnerabilities, specifically WAF bypass. It highlights two payloads for XSS and four for SQL injection, including the Xss0r with a worldlist of 5000 payloads for bypassing. The user expresses frustration about wasting money on the SmartScanner tool. A blog post about this bypass can include details on the SmartScanner tool, the use of open source tools and AI for vulnerability detection, the specific XSS and SQLi payloads mentioned, and the importance of effective WAF bypass techniques.<br />
  438. Check out the original tweet here: https://twitter.com/Ah5495811483065/status/1910623587863527796</p>
  439. ]]></content:encoded>
  441. <wfw:commentRss>https://waf-bypass.com/2025/04/12/waf-bypass-by-ah5495811483065-2/feed/</wfw:commentRss>
  442. <slash:comments>0</slash:comments>
  445. </item>
  446. <item>
  447. <title>WAF bypass by Euro_Phd</title>
  448. <link>https://waf-bypass.com/2025/04/12/waf-bypass-by-euro_phd/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-euro_phd</link>
  449. <comments>https://waf-bypass.com/2025/04/12/waf-bypass-by-euro_phd/#respond</comments>
  451. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  452. <pubDate>Sat, 12 Apr 2025 06:00:02 +0000</pubDate>
  453. <category><![CDATA[Uncategorized]]></category>
  454. <guid isPermaLink="false">http://waf-bypass.com/2025/04/12/waf-bypass-by-euro_phd/</guid>
  455.  
  456. <description><![CDATA[The tweet mentions a potential WAF bypass or load balancer bypass depending on the context. The payload used is &#039;/load balancer bypass&#039;. Further information or context is needed to determine the specific vulnerability type and vendor. This could be a hint at evading web application firewalls or load balancers for potential security bypasses. ??? ??????? [&#8230;]]]></description>
  457. <content:encoded><![CDATA[<p>The tweet mentions a potential WAF bypass or load balancer bypass depending on the context. The payload used is &#039;/load balancer bypass&#039;. Further information or context is needed to determine the specific vulnerability type and vendor. This could be a hint at evading web application firewalls or load balancers for potential security bypasses.</p>
  458. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  459. <p lang="uk" dir="ltr">??? ??????? ??? ????????? ?? ???? ???? WAF bypass, /load balancer bypass, ???? ? ?? ??????</p>
  460. <p>&mdash; ?Dollar (@Euro_Phd) <a href="https://twitter.com/Euro_Phd/status/1910658644401660075?ref_src=twsrc%5Etfw">April 11, 2025</a></p></blockquote>
  461. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  462. ]]></content:encoded>
  464. <wfw:commentRss>https://waf-bypass.com/2025/04/12/waf-bypass-by-euro_phd/feed/</wfw:commentRss>
  465. <slash:comments>0</slash:comments>
  468. </item>
  469. <item>
  470. <title>WAF bypass by Sh_O_A1b</title>
  471. <link>https://waf-bypass.com/2025/04/12/waf-bypass-by-sh_o_a1b/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-sh_o_a1b</link>
  472. <comments>https://waf-bypass.com/2025/04/12/waf-bypass-by-sh_o_a1b/#respond</comments>
  474. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  475. <pubDate>Sat, 12 Apr 2025 05:00:02 +0000</pubDate>
  476. <category><![CDATA[Uncategorized]]></category>
  477. <guid isPermaLink="false">http://waf-bypass.com/2025/04/12/waf-bypass-by-sh_o_a1b/</guid>
  478.  
  479. <description><![CDATA[A new BurpSuite extension has been released that rotates the user agent with every request to bypass WAFs that block users based on User Agent. This simple and easy-to-use extension can be helpful in evading WAF restrictions. It was recently shared with the community in the Bug Bounty and hacker community. An effective method for [&#8230;]]]></description>
  480. <content:encoded><![CDATA[<p>A new BurpSuite extension has been released that rotates the user agent with every request to bypass WAFs that block users based on User Agent. This simple and easy-to-use extension can be helpful in evading WAF restrictions. It was recently shared with the community in the Bug Bounty and hacker community. An effective method for bypassing WAF restrictions based on User Agent filtering.<br />
  481. For more insights, check out the original tweet here: https://twitter.com/Sh_O_A1b/status/1910823013693481124</p>
  482. ]]></content:encoded>
  484. <wfw:commentRss>https://waf-bypass.com/2025/04/12/waf-bypass-by-sh_o_a1b/feed/</wfw:commentRss>
  485. <slash:comments>0</slash:comments>
  488. </item>
  489. <item>
  490. <title>WAF bypass by GREENARM0R</title>
  491. <link>https://waf-bypass.com/2025/04/11/waf-bypass-by-greenarm0r/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-greenarm0r</link>
  492. <comments>https://waf-bypass.com/2025/04/11/waf-bypass-by-greenarm0r/#respond</comments>
  494. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  495. <pubDate>Fri, 11 Apr 2025 06:00:03 +0000</pubDate>
  496. <category><![CDATA[Uncategorized]]></category>
  497. <guid isPermaLink="false">http://waf-bypass.com/2025/04/11/waf-bypass-by-greenarm0r/</guid>
  498.  
  499. <description><![CDATA[The bypass tool enables bypassing security restrictions through HTTPS/TLS, making it easier to bypass IDS/IPS and WAF, as well as restrictions imposed on the firewall. Additionally, it supports SOCKS5 and TUN, with SOCKS5 being ideal for routing tools like proxychains, Burp Suite, or your browser through the tunnel. Check out the original tweet here: https://twitter.com/GREENARM0R/status/1910326158425473514]]></description>
  500. <content:encoded><![CDATA[<p>The bypass tool enables bypassing security restrictions through HTTPS/TLS, making it easier to bypass IDS/IPS and WAF, as well as restrictions imposed on the firewall. Additionally, it supports SOCKS5 and TUN, with SOCKS5 being ideal for routing tools like proxychains, Burp Suite, or your browser through the tunnel.<br />
  501. Check out the original tweet here: https://twitter.com/GREENARM0R/status/1910326158425473514</p>
  502. ]]></content:encoded>
  504. <wfw:commentRss>https://waf-bypass.com/2025/04/11/waf-bypass-by-greenarm0r/feed/</wfw:commentRss>
  505. <slash:comments>0</slash:comments>
  508. </item>
  509. <item>
  510. <title>WAF bypass by KirollosBotros1</title>
  511. <link>https://waf-bypass.com/2025/04/11/waf-bypass-by-kirollosbotros1/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-kirollosbotros1</link>
  512. <comments>https://waf-bypass.com/2025/04/11/waf-bypass-by-kirollosbotros1/#respond</comments>
  514. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  515. <pubDate>Fri, 11 Apr 2025 05:00:02 +0000</pubDate>
  516. <category><![CDATA[Uncategorized]]></category>
  517. <guid isPermaLink="false">http://waf-bypass.com/2025/04/11/waf-bypass-by-kirollosbotros1/</guid>
  518.  
  519. <description><![CDATA[The tweet suggests using SQLMap with the -tamper flag to bypass the WAF for bug bounty or penetration testing purposes. This technique is commonly used for SQL injection vulnerabilities. It is important to note that bypassing a WAF without proper authorization may be against ethical guidelines. It is recommended to report any vulnerabilities responsibly to [&#8230;]]]></description>
  520. <content:encoded><![CDATA[<p>The tweet suggests using SQLMap with the -tamper flag to bypass the WAF for bug bounty or penetration testing purposes. This technique is commonly used for SQL injection vulnerabilities. It is important to note that bypassing a WAF without proper authorization may be against ethical guidelines. It is recommended to report any vulnerabilities responsibly to the appropriate parties.<br />
  521. For more insights, check out the original tweet here: https://twitter.com/KirollosBotros1/status/1910499076178928105. And don’t forget to follow @KirollosBotros1 for more exciting updates in the world of cybersecurity.</p>
  522. ]]></content:encoded>
  524. <wfw:commentRss>https://waf-bypass.com/2025/04/11/waf-bypass-by-kirollosbotros1/feed/</wfw:commentRss>
  525. <slash:comments>0</slash:comments>
  528. </item>
  529. <item>
  530. <title>WAF bypass by AadityaPatil_</title>
  531. <link>https://waf-bypass.com/2025/04/10/waf-bypass-by-aadityapatil_/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-aadityapatil_</link>
  532. <comments>https://waf-bypass.com/2025/04/10/waf-bypass-by-aadityapatil_/#respond</comments>
  534. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  535. <pubDate>Thu, 10 Apr 2025 07:00:02 +0000</pubDate>
  536. <category><![CDATA[Uncategorized]]></category>
  537. <guid isPermaLink="false">http://waf-bypass.com/2025/04/10/waf-bypass-by-aadityapatil_/</guid>
  538.  
  539. <description><![CDATA[The user mentioned using Burp Suite MCP Server with Claude Desktop for WAF bypass testing. This combination proved to be effective in providing WAF bypass requests directly in Repeater without extra work. This toolset can be super helpful for quickly testing different payloads during pentesting activities. #CyberSecurity #BugBounty #WAFBypass Just tried out Burp Suite MCP [&#8230;]]]></description>
  540. <content:encoded><![CDATA[<p>The user mentioned using Burp Suite MCP Server with Claude Desktop for WAF bypass testing. This combination proved to be effective in providing WAF bypass requests directly in Repeater without extra work. This toolset can be super helpful for quickly testing different payloads during pentesting activities. #CyberSecurity #BugBounty #WAFBypass</p>
  541. <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
  542. <p lang="en" dir="ltr">Just tried out Burp Suite MCP Server with Claude Desktop today, and it worked really well. It gave me WAF bypass requests directly in Repeaterno extra work needed.<br />Super helpful for quickly testing different payloads during pentesting <a href="https://twitter.com/hashtag/CyberSecurity?src=hash&amp;ref_src=twsrc%5Etfw">#CyberSecurity</a> <a href="https://twitter.com/hashtag/BugBounty?src=hash&amp;ref_src=twsrc%5Etfw">#BugBounty</a> <a href="https://twitter.com/hashtag/BurpSuite?src=hash&amp;ref_src=twsrc%5Etfw">#BurpSuite</a> <a href="https://twitter.com/hashtag/Claude?src=hash&amp;ref_src=twsrc%5Etfw">#Claude</a></p>
  543. <p>&mdash; Aditya Patil (@AadityaPatil_) <a href="https://twitter.com/AadityaPatil_/status/1909901256681807955?ref_src=twsrc%5Etfw">April 9, 2025</a></p></blockquote>
  544. <p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>
  545. ]]></content:encoded>
  547. <wfw:commentRss>https://waf-bypass.com/2025/04/10/waf-bypass-by-aadityapatil_/feed/</wfw:commentRss>
  548. <slash:comments>0</slash:comments>
  551. </item>
  552. <item>
  553. <title>WAF bypass by Nicatabb</title>
  554. <link>https://waf-bypass.com/2025/04/10/waf-bypass-by-nicatabb/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-nicatabb</link>
  555. <comments>https://waf-bypass.com/2025/04/10/waf-bypass-by-nicatabb/#respond</comments>
  557. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  558. <pubDate>Thu, 10 Apr 2025 06:00:02 +0000</pubDate>
  559. <category><![CDATA[Uncategorized]]></category>
  560. <guid isPermaLink="false">http://waf-bypass.com/2025/04/10/waf-bypass-by-nicatabb/</guid>
  561.  
  562. <description><![CDATA[This is an XSS bypass for Imperva WAF. The payload used is &#039;&#38;gt;&#38;lt;input type=hidden oncontentvisibilityautostatechange=alert(1) style=content-visibility:auto&#38;gt;&#039;. Details of the bypass: The payload exploits the oncontentvisibilityautostatechange attribute to trigger an alert(1) function, allowing an attacker to execute arbitrary JavaScript code. For more technical details, visit the blog post. Check out the original tweet here: https://twitter.com/Nicatabb/status/1909959990778962096]]></description>
  563. <content:encoded><![CDATA[<p>This is an XSS bypass for Imperva WAF. The payload used is &#039;&amp;gt;&amp;lt;input type=hidden oncontentvisibilityautostatechange=alert(1) style=content-visibility:auto&amp;gt;&#039;. Details of the bypass: The payload exploits the oncontentvisibilityautostatechange attribute to trigger an alert(1) function, allowing an attacker to execute arbitrary JavaScript code. For more technical details, visit the blog post.<br />
  564. Check out the original tweet here: https://twitter.com/Nicatabb/status/1909959990778962096</p>
  565. ]]></content:encoded>
  567. <wfw:commentRss>https://waf-bypass.com/2025/04/10/waf-bypass-by-nicatabb/feed/</wfw:commentRss>
  568. <slash:comments>0</slash:comments>
  571. </item>
  572. <item>
  573. <title>WAF bypass by mossad_inside</title>
  574. <link>https://waf-bypass.com/2025/04/10/waf-bypass-by-mossad_inside/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-mossad_inside</link>
  575. <comments>https://waf-bypass.com/2025/04/10/waf-bypass-by-mossad_inside/#respond</comments>
  577. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  578. <pubDate>Thu, 10 Apr 2025 05:00:02 +0000</pubDate>
  579. <category><![CDATA[Uncategorized]]></category>
  580. <guid isPermaLink="false">http://waf-bypass.com/2025/04/10/waf-bypass-by-mossad_inside/</guid>
  581.  
  582. <description><![CDATA[The tweet mentions a successful bypass of the Bangladesh WAF using a curl command with proxy and SSL ignore options. It suggests hiring a UI developer for the website. A blog post can detail the process of the bypass, the implications for the security of the website, and recommendations for securing the WAF against such [&#8230;]]]></description>
  583. <content:encoded><![CDATA[<p>The tweet mentions a successful bypass of the Bangladesh WAF using a curl command with proxy and SSL ignore options. It suggests hiring a UI developer for the website. A blog post can detail the process of the bypass, the implications for the security of the website, and recommendations for securing the WAF against such bypasses.<br />
  584. For more insights, check out the original tweet here: https://twitter.com/mossad_inside/status/1910159504269865020</p>
  585. ]]></content:encoded>
  587. <wfw:commentRss>https://waf-bypass.com/2025/04/10/waf-bypass-by-mossad_inside/feed/</wfw:commentRss>
  588. <slash:comments>0</slash:comments>
  591. </item>
  592. <item>
  593. <title>WAF bypass by gillzzey</title>
  594. <link>https://waf-bypass.com/2025/04/09/waf-bypass-by-gillzzey/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-gillzzey</link>
  595. <comments>https://waf-bypass.com/2025/04/09/waf-bypass-by-gillzzey/#respond</comments>
  597. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  598. <pubDate>Wed, 09 Apr 2025 05:00:02 +0000</pubDate>
  599. <category><![CDATA[Uncategorized]]></category>
  600. <guid isPermaLink="false">http://waf-bypass.com/2025/04/09/waf-bypass-by-gillzzey/</guid>
  601.  
  602. <description><![CDATA[This tweet highlights multiple XSS vulnerabilities and bypass techniques, including PostMessage Source Check Bypass, Parameter Smuggling, WAF Bypass via Hash Tricks, hostname validation bypass using dot trailing, and UserWay XSS via QuerySelector Injection. These techniques can circumvent various web application firewalls. A detailed blog post with technical details is recommended. For more insights, check out [&#8230;]]]></description>
  603. <content:encoded><![CDATA[<p>This tweet highlights multiple XSS vulnerabilities and bypass techniques, including PostMessage Source Check Bypass, Parameter Smuggling, WAF Bypass via Hash Tricks, hostname validation bypass using dot trailing, and UserWay XSS via QuerySelector Injection. These techniques can circumvent various web application firewalls. A detailed blog post with technical details is recommended.<br />
  604. For more insights, check out the original tweet here: https://twitter.com/gillzzey/status/1909604181549498582. And don’t forget to follow @gillzzey for more exciting updates in the world of cybersecurity.</p>
  605. ]]></content:encoded>
  607. <wfw:commentRss>https://waf-bypass.com/2025/04/09/waf-bypass-by-gillzzey/feed/</wfw:commentRss>
  608. <slash:comments>0</slash:comments>
  611. </item>
  612. <item>
  613. <title>WAF bypass by nullret</title>
  614. <link>https://waf-bypass.com/2025/04/08/waf-bypass-by-nullret/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-nullret</link>
  615. <comments>https://waf-bypass.com/2025/04/08/waf-bypass-by-nullret/#respond</comments>
  617. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  618. <pubDate>Tue, 08 Apr 2025 05:00:02 +0000</pubDate>
  619. <category><![CDATA[Uncategorized]]></category>
  620. <guid isPermaLink="false">http://waf-bypass.com/2025/04/08/waf-bypass-by-nullret/</guid>
  621.  
  622. <description><![CDATA[The tweet mentions attempts to bypass Imperva WAF using encoded payloads, null bytes, case-swapping, and time-based delays. The user expresses frustration as the WAF remains resilient. This showcases the challenges faced in bypassing Imperva WAF&#039;s security measures. It would be interesting to explore the specific techniques used and the reasons for their failure in a [&#8230;]]]></description>
  623. <content:encoded><![CDATA[<p>The tweet mentions attempts to bypass Imperva WAF using encoded payloads, null bytes, case-swapping, and time-based delays. The user expresses frustration as the WAF remains resilient. This showcases the challenges faced in bypassing Imperva WAF&#039;s security measures. It would be interesting to explore the specific techniques used and the reasons for their failure in a blog post, highlighting the robustness of Imperva&#039;s security technology.<br />
  624. For more insights, check out the original tweet here: https://twitter.com/nullret/status/1909378176079614104. And don’t forget to follow @nullret for more exciting updates in the world of cybersecurity.</p>
  625. ]]></content:encoded>
  627. <wfw:commentRss>https://waf-bypass.com/2025/04/08/waf-bypass-by-nullret/feed/</wfw:commentRss>
  628. <slash:comments>0</slash:comments>
  631. </item>
  632. <item>
  633. <title>WAF bypass by Allan_K_R</title>
  634. <link>https://waf-bypass.com/2025/04/07/waf-bypass-by-allan_k_r/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=waf-bypass-by-allan_k_r</link>
  635. <comments>https://waf-bypass.com/2025/04/07/waf-bypass-by-allan_k_r/#respond</comments>
  637. <dc:creator><![CDATA[wafbypass]]></dc:creator>
  638. <pubDate>Mon, 07 Apr 2025 07:00:02 +0000</pubDate>
  639. <category><![CDATA[Uncategorized]]></category>
  640. <guid isPermaLink="false">http://waf-bypass.com/2025/04/07/waf-bypass-by-allan_k_r/</guid>
  641.  
  642. <description><![CDATA[The tweet suggests using rotating proxies on a VPN for WAF bypass. This approach can help in creating a large pool of IP addresses to evade WAF detection. Running the tool on a VPS can handle the huge workload efficiently. However, it&#039;s important to note that using rotating proxies for WAF bypass may have legal [&#8230;]]]></description>
  643. <content:encoded><![CDATA[<p>The tweet suggests using rotating proxies on a VPN for WAF bypass. This approach can help in creating a large pool of IP addresses to evade WAF detection. Running the tool on a VPS can handle the huge workload efficiently. However, it&#039;s important to note that using rotating proxies for WAF bypass may have legal and ethical implications, so use it responsibly.<br />
  644. For more details, check out the original tweet here: https://twitter.com/Allan_K_R/status/1908877834698842245</p>
  645. ]]></content:encoded>
  647. <wfw:commentRss>https://waf-bypass.com/2025/04/07/waf-bypass-by-allan_k_r/feed/</wfw:commentRss>
  648. <slash:comments>0</slash:comments>
  651. </item>
  652. </channel>
  653. </rss>
  654.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//waf-bypass.com/feed/

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda