<?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 Malvin Valerian on Medium]]></title>
        <description><![CDATA[Stories by Malvin Valerian on Medium]]></description>
        <link>https://medium.com/@malvinval?source=rss-e094a6b30521------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4TNcSNVXEwlIc5iBavizbw.jpeg</url>
            <title>Stories by Malvin Valerian on Medium</title>
            <link>https://medium.com/@malvinval?source=rss-e094a6b30521------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:30:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@malvinval/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[Stored XSS via CSV File Upload (Writeup)]]></title>
            <link>https://medium.com/@malvinval/stored-xss-via-csv-file-upload-writeup-326df73a468a?source=rss-e094a6b30521------2</link>
            <guid isPermaLink="false">https://medium.com/p/326df73a468a</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Malvin Valerian]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 05:03:49 GMT</pubDate>
            <atom:updated>2025-04-17T05:04:09.858Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello!</p><p>I want to share how I discovered a <a href="https://cwe.mitre.org/data/definitions/79.html">Stored XSS</a> vulnerability via CSV file upload in the <a href="https://wordpress.org/plugins/url-shortify/">URL Shortify WordPress plugin</a>. This vulnerability has been reported, and published as <a href="https://www.cve.org/CVERecord?id=CVE-2025-32134">CVE-2025–32134</a> by <a href="https://patchstack.com/">Patchstack</a>.</p><p>Now, let’s jump into it!</p><p>First of all, I have to install the <a href="https://wordpress.org/plugins/url-shortify/">URL Shortify WordPress plugin</a> in my local WordPress environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kOkntXwcbJRQNL1POewn-w.png" /><figcaption>URL Shortify Wordpress Plugin Download Page</figcaption></figure><p>After that, I opened up the WordPress admin page, add new link at <strong><em>/wp-admin/admin.php?page=us_links&amp;action=new</em></strong>. Here I fill all required data to add new link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zDuIC_Z2ZvUvBehpZGYxdA.png" /><figcaption>Page to Create New Link</figcaption></figure><p>Here, I tried to inject the <strong>Title</strong> input with this simple XSS payload:</p><p>/*iframe/src*/&lt;iframe/src=”&lt;iframe/src=@”/onload=alert(document.cookie) /*iframe/src*/&gt;</p><p>and save the link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*AZPTM9_xK-Bq62_lxIz_2Q.png" /></figure><p>Unfortunately, this technique does not seem to be work. No XSS trigerred.</p><p>But, I found an interesting feature where I can upload a CSV file. This feature can be used to import multiple links at once. The feature can be found at <strong><em>/wp-admin/admin.php?page=us_tools&amp;action=csv</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*V6vxNtnIGiFcJIH9nVJMuA.png" /><figcaption>URL Shortify Import Links Page</figcaption></figure><p>What will happen if I inject the XSS payload inside the CSV file? Let’s check it out!</p><p>First, I download the CSV file template. The template can be downloaded at <strong><em>/wp-content/plugins/url-shortify/lite/includes/Admin/Templates/sample.csv</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HP02GQ_gVb5rYVS2hZtRbQ.png" /><figcaption>CSV File Structure</figcaption></figure><p>Here I can inject the XSS payload to some columns such as <strong>Title, Description, </strong>and <strong>Groups</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*ZeNeWAMwcLArDXCeXWqEIA.png" /></figure><p>After that, I simply upload the CSV file and go back to the links page at <strong><em>/wp-admin/admin.php?page=us_links</em></strong>. Guess what happened?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eQgKhU3iAaLc2Z4iPRTGrQ.png" /><figcaption>XSS Trigerred</figcaption></figure><p>The CSV file stored to the database, and the XSS executed. I can confirm that this is a Stored XSS vulnerability.</p><p><strong>Timeline:</strong></p><p><em>16 Jan 2025 </em>: Reported to Patchstack</p><p><em>04 Apr 2025 </em>: CVE Published by Patchstack</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=326df73a468a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Privilege Escalation via Registration Feature Writeup]]></title>
            <link>https://medium.com/@malvinval/privilege-escalation-via-registration-feature-writeup-3f02c66b2391?source=rss-e094a6b30521------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f02c66b2391</guid>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-writeup]]></category>
            <dc:creator><![CDATA[Malvin Valerian]]></dc:creator>
            <pubDate>Sun, 30 Mar 2025 13:44:37 GMT</pubDate>
            <atom:updated>2025-03-30T13:45:57.242Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>👋 Hello, fellow security geeks!</strong></p><p>Sometimes, the biggest vulnerabilities hide in the most basic features. Recently, I was testing a web application when I stumbled upon a critical<strong> privilege escalation bug</strong> — all because the system trusted user input a little too much.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*ACMcHCzpbR1tKEqETGbcKg.png" /><figcaption>Privilege Escalation Illustration</figcaption></figure><h4><strong>🧐 The Discovery</strong></h4><p>I was casually testing a web application when I decided to take a closer look at its <strong>registration process</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/458/1*A_Gh6YS0I-Qhkm9z_zb5oQ.png" /><figcaption>Registration Form</figcaption></figure><p>Nothing fancy — just the usual fields: name, username, email, phone, password, and… a <strong>Role</strong> field. That instantly caught my attention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*chkbM9FPqGA-L7inJ7uoDg.png" /><figcaption>Registration Request Body (Burp)</figcaption></figure><pre>{<br>  &quot;username&quot;: &quot;attackerxx&quot;,<br>  &quot;name&quot;: &quot;attackerxx&quot;,<br>  &quot;email&quot;: &quot;attackerxx@gmail.com&quot;,<br>  &quot;phone&quot;: &quot;87897165141&quot;,<br>  &quot;password&quot;: &quot;C0b44tt4ck**&quot;,<br>  &quot;password&quot;: &quot;C0b44tt4ck**&quot;,<br>  &quot;role&quot;: &quot;User&quot;<br>}</pre><p>Most applications don’t allow users to <strong>self-assign roles</strong> during registration. The server should automatically set it to a <strong>default</strong> value, like “User.” But what if I could change it?</p><p>I modified &quot;role&quot;: &quot;User&quot; to &quot;role&quot;: &quot;Admin&quot; and forwarded the request.</p><pre>{<br>  &quot;username&quot;: &quot;attackerxx&quot;,<br>  &quot;name&quot;: &quot;attackerxx&quot;,<br>  &quot;email&quot;: &quot;attackerxx@gmail.com&quot;,<br>  &quot;phone&quot;: &quot;87897165141&quot;,<br>  &quot;password&quot;: &quot;C0b44tt4ck**&quot;,<br>  &quot;password&quot;: &quot;C0b44tt4ck**&quot;,<br>  &quot;role&quot;: &quot;Admin&quot;<br>}</pre><p>I checked my newly created account, logged in… and yay — I am an <strong>Admin</strong>! No privilege checks, no approval process, just instant escalation. I now had access to <strong>admin-only</strong> management features, including <strong>Products, Orders, Discounts, Categories, User accounts, Product pickup requests.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hMC_L9O5fQvMfVh7LnA4PQ.png" /><figcaption>Admin Page (Orders)</figcaption></figure><h4>🚨 Why This Happens?</h4><p>This kind of vulnerability occurs when role assignments rely on user input instead of being enforced server-side. The application should ignore any role parameter provided by the user and assign roles securely based on predefined logic. The server should ignore or sanitize any <strong>Role</strong> field provided in the request.</p><p>I hope this write-up helps developers and security professionals stay vigilant against similar issues. Stay secure, and happy hunting! 🔎💻</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f02c66b2391" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stored XSS via JSON File Upload]]></title>
            <link>https://medium.com/@malvinval/stored-xss-via-json-file-upload-poc-9a1063bba5b8?source=rss-e094a6b30521------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a1063bba5b8</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Malvin Valerian]]></dc:creator>
            <pubDate>Sat, 25 Jan 2025 08:21:43 GMT</pubDate>
            <atom:updated>2025-01-25T08:22:26.460Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello!</p><p>I want to share how I discovered a <a href="https://cwe.mitre.org/data/definitions/79.html">Stored XSS</a> vulnerability via JSON file upload in the <a href="https://wordpress.org/plugins/ip2location-country-blocker/">IP2Location Country Blocker WordPress plugin</a>. This vulnerability has been reported, and published as <a href="https://www.cve.org/CVERecord?id=CVE-2025-24731">CVE-2025–24731</a> by <a href="https://patchstack.com/">Patchstack</a>.</p><p>Now, let’s jump into it!</p><p>First of all, I have to install the <a href="https://wordpress.org/plugins/ip2location-country-blocker/">IP2Location Country Blocker WordPress plugin</a> in my local WordPress environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kPpRf_toHzSL679BlyunCw.png" /><figcaption>IP2Location WordPress Download Page</figcaption></figure><p>After that, I opened up the WordPress admin page, and jump into the plugin settings page at <strong><em>/wp-admin/admin.php?page=ip2location-country-blocker-settings</em></strong>. Here I found an interesting feature where I can upload a JSON file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/1*38gqXR8HZ8JLcptb7bdbZw.png" /><figcaption>JSON File Upload Feature</figcaption></figure><p>As you can see, the plugin is also provides the JSON file template. I downloaded the template, and open it up. The JSON template looks like this:</p><pre>{<br>    &quot;ip2location_country_blocker_access_email_notification&quot;: &quot;none&quot;,<br>    &quot;ip2location_country_blocker_api_key&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_backend_auto_block_threshold&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_backend_banlist&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_backend_block_mode&quot;: &quot;1&quot;,<br>    &quot;ip2location_country_blocker_backend_block_proxy&quot;: &quot;0&quot;,<br>    &quot;ip2location_country_blocker_backend_bots_list&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_frontend_ip_whitelist&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_frontend_option&quot;: &quot;1&quot;,<br>    &quot;ip2location_country_blocker_frontend_redirect_url&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_frontend_skip_bots&quot;: &quot;1&quot;,<br>    &quot;ip2location_country_blocker_frontend_whitelist_logged_user&quot;: &quot;1&quot;,<br>    &quot;ip2location_country_blocker_log_enabled&quot;: &quot;1&quot;,<br>    &quot;ip2location_country_blocker_lookup_mode&quot;: &quot;bin&quot;,<br>    &quot;ip2location_country_blocker_px_api_key&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_px_database&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_px_lookup_mode&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_real_ip_header&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_session_message&quot;: &quot;&quot;,<br>    &quot;ip2location_country_blocker_token&quot;: &quot;your_not_so_secret_token&quot;<br>}</pre><p>I set all the value with this simple payload</p><p><em>&lt;svg onload=alert(document.cookie)&gt;</em></p><p>After that, I upload the JSON file. Guess what happened?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJkvp-cgxFFhyqROOJ3sTw.png" /><figcaption>XSS Triggered</figcaption></figure><p>The JSON file stored to the database, and the XSS executed. I can confirm that this is a Stored XSS vulnerability.</p><p>After many tries, I found out the only vulnerable attribute is “<strong>ip2location_country_blocker_px_database”</strong>. So, this simple exploit below will trigger the XSS:</p><pre>{<br>    &quot;other_key&quot;:&quot;&quot;,<br>    &quot;ip2location_country_blocker_px_database&quot;: &quot;&lt;svg onload=alert(document.cookie)&gt;&quot;,<br>    &quot;other_key&quot;: &quot;&quot;<br>}</pre><p>Aight, that’s all. Pretty boring, right? LOL.</p><p><strong>Timeline:</strong></p><p><em>17 Jan 2025 </em>: Reported to Patchstack</p><p><em>24 Jan 2025 </em>: CVE Published by Patchstack</p><p><strong>Thanks for coming!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a1063bba5b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CVE-2024–54385 | WordPress Plugin]]></title>
            <link>https://medium.com/@malvinval/cve-2024-54385-wordpress-plugin-7ff0f8e5ad1d?source=rss-e094a6b30521------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ff0f8e5ad1d</guid>
            <category><![CDATA[cve]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Malvin Valerian]]></dc:creator>
            <pubDate>Tue, 17 Dec 2024 05:06:06 GMT</pubDate>
            <atom:updated>2025-01-25T07:21:18.465Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>CVE-2024–54385 | Unauthenticated SSRF in WordPress Plugin</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*lk_jA_mIsfilbeDwnmXvpw.png" /></figure><p>Hello!</p><p>I discovered a <a href="https://cwe.mitre.org/data/definitions/918.html">Server-Side Request Forgery</a> (SSRF) vulnerability in the <a href="https://wordpress.org/plugins/radio-player/"><strong>Radio Player</strong></a> WordPress plugin, assigned as <a href="https://www.cve.org/CVERecord?id=CVE-2024-54385"><strong>CVE-2024–54385</strong></a>. This flaw allows attackers to force the server to make arbitrary requests, which can be leveraged to takeover a server if a website using a Google Cloud Platform (GCP) or AWS environment. For example, for GCP environment, attacker can use http://169.254.169.254/computeMetadata/v1/.</p><p><strong>CVSS</strong>: 7.2<br><strong>CWE: </strong>CWE-918<strong> (</strong><a href="https://cwe.mitre.org/data/definitions/918.html">Server-Side Request Forgery</a><strong>)</strong></p><p><strong>Steps to Reproduce</strong>:</p><ol><li><a href="https://demo.softlabbd.com/?product=radio-player">Register a demo account</a> &amp; login</li><li>In WordPress admin page, navigate to Settings &gt; Proxy Settings</li><li>Enable HTTP Proxy</li><li>Delete the proxy URL</li><li>Save changes</li><li>Insert file:///etc/passwd in radio_player_play parameter. Example: https://demo.softlabbd.com/&lt;account_demo_id&gt;/?radio_player_play=file:///etc/passwd</li></ol><p><strong>Timeline:</strong></p><p><em>02 Nov 2024 </em>: Reported to Patchstack</p><p><em>14 Dec 2024 </em>: CVE Published by Patchstack</p><p><strong>That’s all. Thanks for coming!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ff0f8e5ad1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SSRF to Server Takeover PoC (Bug Bounty Writeup)]]></title>
            <link>https://medium.com/@malvinval/ssrf-to-server-takeover-poc-bug-bounty-writeup-82d6715e333d?source=rss-e094a6b30521------2</link>
            <guid isPermaLink="false">https://medium.com/p/82d6715e333d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Malvin Valerian]]></dc:creator>
            <pubDate>Tue, 06 Aug 2024 05:51:24 GMT</pubDate>
            <atom:updated>2024-08-06T05:51:24.686Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi, there! In this post, I’ll explain how I discovered a critical vulnerability that allowed me to take over a server with <strong>root access</strong>, without any restrictions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*wHw-q3_eSVzCOYPnCAtUkg.png" /></figure><h4>What is SSRF Attack?</h4><p>Server-Side Request Forgery (SSRF) is a type of attack that allows an attacker to manipulate a server into making requests on their behalf. By performing an SSRF attack, attackers can send requests from the server to internal systems, and accessing sensitive informations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*twAdZFXcaROUaR5OWv0AgA.jpeg" /></figure><h4>Proof of Concept</h4><p>During the analysis, I noticed that the web app provides a radio streaming feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*wVCem2EZwvzO_WZ0UXM82Q.jpeg" /><figcaption>radio streaming feature</figcaption></figure><p>At this point, I open the Network tab to view the details of the request when I pressed the play button. I found that the web app has a request parameter named source_file used to specify the URL of the MP3 file to be streamed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*zYq_Ca9hxsHvEbvPTdv4bw.png" /><figcaption>mp3 file GET request</figcaption></figure><p>I simply modify the value to http://169.254.169.254/computeMetadata/v1. In this case, the URL corresponds to the <strong>Google Cloud Platform</strong><em> </em>metadata endpoint. What do you think will happen?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VuHlZdeYMzx1KbJ7V2RedQ.png" /><figcaption>sensitive files as response</figcaption></figure><p>Wow! the server fetches data from the specified URL. In this case, it returns metadata including SSH configuration details. Specifically, a file named user_data contains sensitive information such as SSH credentials (username &amp; plain text password).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WCI87MCHrM16u9pKvwY0-g.png" /><figcaption>ssh credentials</figcaption></figure><p>Now I have a full control over the server, including the ability to manipulate server settings and access internal applications.</p><h4>Recommended Mitigation</h4><ul><li><strong>URL Whitelisting:</strong> Restrict the URLs that can be accessed by the server to only known, safe endpoints. Implement a whitelist of allowed domains and paths.</li><li><strong>Input Validation:</strong> Validate and sanitize user inputs to ensure that they do not contain malicious URLs or request patterns.</li><li><strong>Access Controls:</strong> Ensure that sensitive endpoints and internal resources are protected and not accessible from external requests.</li></ul><p><strong>I suggest you to learn more about SSRF</strong>:</p><ul><li>PortSwigger: <a href="https://portswigger.net/web-security/ssrf">https://portswigger.net/web-security/ssrf</a></li><li>Disclosed PoCs in HackerOne</li></ul><p>I hope you find this post useful. If you have any questions or feedback, feel free to reach out. Happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82d6715e333d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>