<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bug Bounty on Jack Taylor</title><link>https://jacktaylor.tech/tags/bug-bounty/</link><description>Recent content in Bug Bounty on Jack Taylor</description><generator>Hugo</generator><language>en</language><managingEditor>jack@jacktaylor.tech (Jack Taylor)</managingEditor><webMaster>jack@jacktaylor.tech (Jack Taylor)</webMaster><lastBuildDate>Sun, 12 Apr 2026 00:47:49 +0900</lastBuildDate><atom:link href="https://jacktaylor.tech/tags/bug-bounty/index.xml" rel="self" type="application/rss+xml"/><item><title>How I found SQL injection on 100,000 WordPress sites</title><link>https://jacktaylor.tech/2026/04/how-i-found-sql-injection-on-100000-wordpress-sites/</link><pubDate>Sun, 12 Apr 2026 00:47:49 +0900</pubDate><author>jack@jacktaylor.tech (Jack Taylor)</author><guid>https://jacktaylor.tech/2026/04/how-i-found-sql-injection-on-100000-wordpress-sites/</guid><description>&lt;p&gt;I recently reported an unauthenticated &lt;a href="https://en.wikipedia.org/wiki/SQL_injection"&gt;SQL injection&lt;/a&gt; in &lt;a href="https://www.relevanssi.com/"&gt;Relevanssi&lt;/a&gt;, a WordPress search plugin that was active on more than 100,000 sites. There were two things that made this bug especially fun to work on: first, a type confusion issue where input that only &lt;em&gt;looked&lt;/em&gt; like a numeric term ID could carry extra SQL with it, and second, an exploitation trick where one SQL injection payload was smuggled inside another in order to get around the limitations of the first query.&lt;/p&gt;</description></item><item><title>Proxy OWASP ZAP through a VPS</title><link>https://jacktaylor.tech/2022/04/proxy-owasp-zap-through-a-vps/</link><pubDate>Sat, 02 Apr 2022 11:45:00 +0900</pubDate><author>jack@jacktaylor.tech (Jack Taylor)</author><guid>https://jacktaylor.tech/2022/04/proxy-owasp-zap-through-a-vps/</guid><description>&lt;p&gt;If you do any kind of penetration testing or bug bounty hunting from your home
PC, then as a necessity you will be sending malicious-looking traffic to your
target. If your target happens to be protected by Akamai or CloudFlare, and you
don&amp;rsquo;t take any special precautions, then unfortunate things may happen.
Unfortunate, as in your home IP gets &lt;a href="https://www.doyler.net/security-not-included/akamai-internet-banned"&gt;blocked from half the sites on the
internet&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To avoid this, you need to make your web traffic look like it came from a
different IP address than it actually did. This means using some kind of proxy
server. There are a few different ways you can do this, but my preferred way is
to use a virtual private server (VPS) rented out from a cloud provider.&lt;/p&gt;</description></item></channel></rss>