<?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 nguyenchinh on Medium]]></title>
        <description><![CDATA[Stories by nguyenchinh on Medium]]></description>
        <link>https://medium.com/@will.star?source=rss-08613de00c1a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oZejWnmhvtFYWUILp3DfYg.png</url>
            <title>Stories by nguyenchinh on Medium</title>
            <link>https://medium.com/@will.star?source=rss-08613de00c1a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:12:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@will.star/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[When "Duplicate" is an affirmation of your skill.]]></title>
            <link>https://medium.com/@will.star/when-duplicate-is-an-affirmation-of-your-skill-9d1261e3f6b2?source=rss-08613de00c1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d1261e3f6b2</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[nguyenchinh]]></dc:creator>
            <pubDate>Thu, 09 Apr 2026 07:49:56 GMT</pubDate>
            <atom:updated>2026-04-09T09:03:29.930Z</atom:updated>
            <content:encoded><![CDATA[<h3>A large system with a wide attack surface.</h3><p>During an evening of searching for targets on Bug Bounty platforms, I decided to focus on a fairly well-known technology service provider. This is a system with a complex infrastructure, which means that subdomains are often easily overlooked in the security validation process.</p><h3>The vulnerability from URL parameters</h3><p>During my research, I came across a file management website.</p><p>The most striking detail was the &#39;?prefix=&#39; parameter in the address bar.</p><p>Normally, parameters like this are used to filter the displayed content.</p><p>My immediate thought was:</p><p>&quot;Does the system check the data I enter before returning it to the browser?&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/228/1*4va8rmIaNHdCkdu34YHgBA.gif" /></figure><p>I started by inserting a simple HTML code snippet. Instead of a regular search string, I used the onclick attribute nested within a text formatting tag:</p><pre>&lt;i onclick=alert(1)&gt;Click here&lt;/i&gt;<br></pre><p>Immediately after pressing Enter, the browser did not display plain text but rendered an italicized line of text. When I clicked on it, the alert(1) dialog box appeared.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EU5X1aUhbv0G1BXbP_thUQ.png" /></figure><blockquote>Technical analysis: This is a Reflected Cross-Site Scripting (XSS) vulnerability. The system has taken data directly from the URL and inserted it into the website’s source code without filtering (sanitization) or encoding.</blockquote><h3>The bitter fruit called Duplicate</h3><p>Shortly after submitting the report, I received a response from the Triage team.</p><p>The report status changed from Triage to Duplicate.</p><p>It turned out that, not long before, another researcher had discovered and correctly reported this vulnerability. Although the vulnerability was re-evaluated from Medium (4.3) to Medium (5.4), the reward (Bounty) would only go to the first reporter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*j3k2oTNnigw7Ib3LDKRx9g.webp" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d1261e3f6b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When dev‑server whispers: a bug hunter’s journey discovering CVE‑2025‑30208 on a government portal.]]></title>
            <link>https://medium.com/@will.star/when-dev-server-whispers-a-bug-hunters-journey-discovering-cve-2025-30208-on-a-government-portal-6e7509854acc?source=rss-08613de00c1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e7509854acc</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[hacks]]></category>
            <category><![CDATA[will-star]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[cve-2025-30208]]></category>
            <dc:creator><![CDATA[nguyenchinh]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 20:10:52 GMT</pubDate>
            <atom:updated>2025-10-16T20:22:31.398Z</atom:updated>
            <content:encoded><![CDATA[<h4>Whispers of the Dev-Server: The Journey of a Bug Hunter Discovering CVE‑2025‑30208 on the Government Portal.</h4><p>Hello hackers, my handle is Will.Star. I’m a security researcher and bug bounty hunter who loves finding real‑world vulnerabilities. I found my target during a social engineering/networking trip.</p><h4>1. The hunt begins</h4><p>I started with a series of light checks: inspecting public headers, looking at robots.txt, checking for a sitemap if one existed, and noting subdomains. This was non‑intrusive reconnaissance — no force, no exploitation.<br>After hours of probing, I paused on a particular subdomain and a closer inspection revealed that the site was built with Vite.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*IrAVAh09WgHqhDcBUgia2w.png" /></figure><p>I immediately ran dirsearch to look for hidden directories. I also checked the site’s /main.js file. It proved very useful for deeper discovery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*vWMSJVBUSQptdqMaCCwWPw.png" /></figure><blockquote>I found some important points in it like:<br>* The app is SPA Angular, calling API on <a href="https://xxxx.xxxx.xxx.xxx/">https://xxxx.xxxx.xxx.xxx</a> (saved in environment.baseUrl).<br>* The JWT token is saved in localStorage under key token-pladiermo, there is a validateToken function that decodes the payload part with atob(token.split(‘.’)[1]) and compares exp to determine the operation; if active, the client will call more API to set user/menu/visit and save more data to localStorage.<br>* Login calls endpoint /identidad/auth/login (login POST) and the token is saved after receiving data.data.token. There is a password recovery + password change page on client side.<br>* Many client-side services build explicit RESTful routes (e.g. users: environment.baseUrl + environment.identidad + environment.users with endpoints like /table?active=&amp;page=&amp;size=, /${id}, create, ?id= for update/delete, getMenu(userId) etc.). These API paths are heavily “formatted” and predictable.</blockquote><h4>2. The harsh truth</h4><p>I spent some time learning about Vite to be able to exploit it, we need to understand it.</p><blockquote>*********************************************************************<br>Vite is one of the most popular front-end development tools, supporting thousands of React, Vue and other modern JavaScript projects.</blockquote><p>After a period of research and continuous efforts to penetrate, I discovered the vulnerability CVE 2025–30208 existing in the government website system.</p><blockquote>CVE 2025–30208<br>Publication Date: March 25, 2025<br>Severity Level:<br>HIGH CNA Score: 5.3</blockquote><h4>3. Technical details</h4><p>If you tweak the URL properly, you can bypass these restrictions. By adding “raw” or “import&amp;raw” to the file request URL, you will *bypass* the allowlist and get the raw contents of any file, as long as you know the path and that the file exists.<br>Let’s assume a public Vite development server application. In most setups, requesting a sensitive file like /etc/passwd (Linux) or a configuration file outside the project root directory will be rejected:</p><pre>GET /@fs/etc/passwd   --&gt; 403 Forbidden</pre><p><strong><em>But with the “skip” trick, everything changes.</em></strong></p><pre>GET /@fs/etc/passwd?raw?? --&gt; 200 OK</pre><p><strong><em>or</em></strong></p><pre>GET /@fs/etc/passwd?import&amp;raw?? --&gt; 200 OK</pre><p>And surprisingly, I successfully exploited a website belonging to the government of a state XXX. This surprised me, because they do not regularly upgrade or secure their systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mu8-ePfqmaStRygS97-jWg.png" /></figure><p>I immediately reported it to their national cybersecurity incident response team. And got a response in less than 8 hours (from the time of reporting).</p><h4>4. Minimize the risk</h4><p><strong><em>Patch Immediately! If you are running an older version, upgrade now.</em></strong></p><pre>npm install vite@latest<br># or for a specific branch<br>npm install vite@6.2.3</pre><p>If you must use Vite on an older version (not recommended), never leave the dev server connected to the internet. Run on localhost only for development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e7509854acc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CVE-2025–44148: Cross Site Scripting (XSS) vulnerability on a small business.]]></title>
            <link>https://medium.com/@will.star/cve-2025-44148-cross-site-scripting-xss-vulnerability-on-a-small-business-f88f109262f6?source=rss-08613de00c1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f88f109262f6</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[xss-attack]]></category>
            <dc:creator><![CDATA[nguyenchinh]]></dc:creator>
            <pubDate>Sat, 26 Jul 2025 17:26:01 GMT</pubDate>
            <atom:updated>2025-07-26T17:26:01.985Z</atom:updated>
            <content:encoded><![CDATA[<p>I am Will Star a security newbie. Today I will talk about my little exploration in finding vulnerabilities in enterprise web and how I identified and exploited them.</p><p>This topic will be about a recently disclosed vulnerability. It is CVE-2025–44148.</p><h3><strong>CVE-2025–44148</strong></h3><p>CVE-2025–44148 is a Cross Site Scripting (XSS) vulnerability in MailEnable before v10 that allows remote attackers to execute arbitrary code via the failure.aspx element.</p><h3><strong>Exploitation Journey</strong></h3><p>After a memorable day off, I’m back at work. Today I received a request to do a penetration test for a small business. As usual, I started with the basics by using subfinder and assetfinder to automatically find subdomains. It’s no surprise that my target turned up nearly 70 subdomains. This would have been very time consuming if we had used manual testing to see which domains were live or exploitable.so i used the command:</p><blockquote>httpx -l ****.txt -title -tech-detect -status-code -threads 50 -o ****.txt</blockquote><p>to determine which domain is alive and it was effective and time saving.</p><p>The next thing I usually do is determine what technology is being used by the web and whether it is outdated by using the command “whatweb”.</p><p>The result I see is a subdomain “pop.*******” returning status code 200, same MailEnable WebMail header and technology used is ASP.NET 4.0.30319, server Microsoft-IIS/10.0 when i access that domain name and see the following appear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9qA4ArLT9asqHPcnQxGew.png" /></figure><p>I immediately tried common vulnerabilities like SQL and XSS in both the user parameter and the pass parameter. But that failed.</p><p>Not giving up there i went further by using the command</p><blockquote>ffuf -u <a href="https://pop.*****/editor/FUZZ">https://pop.*****/</a>Mondo/lang/sys/<a href="https://pop.*****/editor/FUZZ">FUZZ</a> -w /usr/share/seclists/Discovery/Web-Content/common.txt -mc 200,302 -ac</blockquote><p>to fuzz the endpoint in the sensitive directory. And “Failure.aspx” appears. When I try to access it, I get the message: “Authentication Failed: Unknown or Disabled User!” But what caught my attention was that the URL had a parameter state=19753 — could it be reflected?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*MwDmNSfi2759hasWE3E80Q.png" /></figure><p>I have used basic XSS payload but all failed, I have also used bypass payload but all failed. But the server does not give any error or display any information.</p><p>After a while of digging i found something interesting and decided to try that parameter again and…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpya1cxrcPElzUlbFkteFQ.png" /></figure><p>Xss has appeared. I opened DevTools → Sources tab and saw the following JavaScript:</p><blockquote>window.location = “login.aspx?UserID=&amp;State=19753**********.domain);function test(){“;</blockquote><p>The website had no escaping, no encoding, no filtering. And my payload went straight into the script as if it were a natural part. I then used nuclei to verify if this was a known vulnerability and the result CVE-2025–44148 was returned — medium severity.</p><p>I continued to test if the system was IP-based and returned 302 with the message:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*XzBlOETzu_keGSjnn5tepw.png" /></figure><p>This shows the high possibility of IP-based authorization — one more door to bypass if XSS + CSRF is combined…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f88f109262f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Detect and exploit basic Stored XSS vulnerability. And nothing special :(]]></title>
            <link>https://medium.com/@will.star/detect-and-exploit-basic-stored-xss-vulnerability-and-nothing-special-c350e0f50df4?source=rss-08613de00c1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c350e0f50df4</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[xss-attack]]></category>
            <dc:creator><![CDATA[nguyenchinh]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 18:44:58 GMT</pubDate>
            <atom:updated>2025-07-19T10:53:31.183Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Phát hiện và khai thác lỗ hổng Stored XSS cơ bản. Không có gì đặc biệt :(</strong></h4><blockquote>Bắt đầu bằng sự tò mò</blockquote><p>Một ngày đẹp trời, tôi vào một trang web thương mại điện tử chỉ để nghịch ngợm một chút. Là một người làm bảo mật, tôi thường tìm kiếm và nhập các trường đáng ngờ mà tôi nghĩ có thể chứa lỗ hổng bảo mật, chẳng hạn như trường tìm kiếm, và tôi đã sử dụng một lệnh cơ bản để kiểm tra lỗ hổng:</p><pre>&lt;script&gt;cảnh báo(&#39;XSS&#39;)&lt;/script&gt;</pre><p>Và… chẳng có gì xảy ra cả. Không cửa sổ bật lên, không lỗi, không hành vi đáng ngờ nào. Tôi nghĩ: &quot;Chắc web đang thoát hoặc lọc dữ liệu đầu vào&quot;. Sau một hồi, tôi đã thử mọi cách để khai thác <strong>XSS</strong> và gần như định bỏ qua lỗi này cho đến khi một ý tưởng lóe lên: &quot;Hãy đi sâu hơn — khu vực người dùng thường là nơi mọi người bất cẩn nhất&quot;.</p><blockquote>Tạo tài khoản người dùng</blockquote><p>Tôi nhanh chóng tạo một tài khoản, đăng nhập và bắt đầu khám phá mọi thứ có thể. Và tôi dừng lại ở mục &quot;Quản lý Địa chỉ&quot; — nơi người dùng có thể thêm địa chỉ giao hàng. Trang này có nhiều biểu mẫu, nhiều trường nhập liệu: tên người nhận, số điện thoại, địa chỉ chi tiết…</p><p>Tôi bắt đầu nhập thông tin sau vào ô Họ và tên:</p><pre>&lt;script&gt;cảnh báo(tài liệu.tên miền)&lt;/script&gt;</pre><p>Nhấn <strong>&quot;Lưu&quot;</strong> , tải lại trang và... không có gì xảy ra. Vì tôi đã bị <em>Cloudflare/WAF</em> chặn . Nhưng tôi ngay lập tức nghĩ đến việc bỏ qua Cloudfl, <strong>Bùm!</strong> Một hộp thoại hiện lên với <strong><em>******.com</em></strong> .</p><p>Không chỉ trường Họ tên đầy đủ bị ảnh hưởng mà một số trường khác cũng bị ảnh hưởng bởi lỗ hổng này.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*YfDpb3fyDulRZ0HLg4MuVA.png" /></figure><p>Và tôi đã khai thác thành công lỗ hổng <strong>Stored XSS</strong> . Finally a report for the <strong>developer</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c350e0f50df4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>