<?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 Yousef A. Menshawy on Medium]]></title>
        <description><![CDATA[Stories by Yousef A. Menshawy on Medium]]></description>
        <link>https://medium.com/@m3nsho?source=rss-a81751561af3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DI5McKo13ex5P4lUH_WMoA.jpeg</url>
            <title>Stories by Yousef A. Menshawy on Medium</title>
            <link>https://medium.com/@m3nsho?source=rss-a81751561af3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:26:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@m3nsho/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[One Request, Two Parameters, Zero Validation]]></title>
            <link>https://medium.com/@m3nsho/one-request-two-parameters-zero-validation-2092a17e7824?source=rss-a81751561af3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2092a17e7824</guid>
            <category><![CDATA[business-logic-flaw]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Yousef A. Menshawy]]></dc:creator>
            <pubDate>Wed, 20 May 2026 19:59:32 GMT</pubDate>
            <atom:updated>2026-05-20T19:59:32.394Z</atom:updated>
            <content:encoded><![CDATA[<p>وقُلْ رَبِّ زِدْنِي عِلْمًا</p><p><em>Hey, my name is </em><strong>Yousef Elmenshawy</strong><em>. I’m a security researcher and bug hunter on YesWeHeck.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*76FI282NoIpewnHUBsxe4g.jpeg" /></figure><p><em>In this write-up, I’ll walk you through one of my recent accepted Bug Bounty findings which I discovered in a private program, I’ll call it test.com. This finding was inside the payment flow and had a direct financial impact on the platform. This one was especially fun because it started as a low severity report and evolved into something more impactful!!</em></p><p><strong>Discovery</strong></p><p>While my friend and I were exploring the store section of test.com, we started intercepting requests during the product purchase flow. One request got all our attention — the request responsible for initiating a purchase request which contained two interesting parameters value and amount.</p><p>Seeing these parameters is suspicious I guess..</p><h3>Finding 1 — The First Try</h3><p>Our first test was straightforward; we intercepted the purchase request and modified the value parameter to an arbitrary number. The request went down through and a charge was initiated from my bank — but the product never appeared in my cart.</p><p>The modified value wasn’t reflected on the account side, so the impact was limited. We reported it immediately, it was triaged but accepted as a low severity finding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYqXN3JxndoA-_SFp17yFg.png" /></figure><h3>Finding 2 — The Real Impact</h3><p>My friend suggested we go back and look harder at the same request. That’s when we noticed the amount parameter sitting right there alongside value.</p><p>We wondered what if we tampered the amount to a negative value while tampering the value parameter..</p><p>We tested this case — and the purchase went through <strong>SUCCESSFULLY!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tf9tEubjELHx4t8hFvkKXQ.png" /></figure><p>Instead of being charged the original price of like 1000$, the transaction processed for just 1$.</p><p>The platform accepted the manipulated amount without any server-side validation.</p><h3>Impact</h3><blockquote>This finding allowed an attacker to purchase products at low prices by manipulating payment parameters. The financial impact to the platform is clear — any product in the store could be bought for much lower than its real price, causing direct financial loss.</blockquote><p>Feel free to connect with me :)</p><p>Twitter: <a href="https://x.com/meenshooo">@meenshooo</a></p><p>Linkedin: <a href="https://www.linkedin.com/in/m3nsho/">@m3nsho</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2092a17e7824" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>