<?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 Prizmo on Medium]]></title>
        <description><![CDATA[Stories by Prizmo on Medium]]></description>
        <link>https://medium.com/@prizmo225?source=rss-cd2960288c27------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lkGH3GRjiGzPDdBiNgwscw.jpeg</url>
            <title>Stories by Prizmo on Medium</title>
            <link>https://medium.com/@prizmo225?source=rss-cd2960288c27------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:17:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prizmo225/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[Hidden in UI, Exposed in API: Sensitive User Info Leak]]></title>
            <link>https://medium.com/@prizmo225/hidden-in-ui-exposed-in-api-sensitive-user-info-leak-5c0b43bded77?source=rss-cd2960288c27------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c0b43bded77</guid>
            <dc:creator><![CDATA[Prizmo]]></dc:creator>
            <pubDate>Fri, 14 Nov 2025 15:33:26 GMT</pubDate>
            <atom:updated>2025-11-14T15:33:26.226Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*iyLIJmXGUtrjbPlPlXv88A.jpeg" /></figure><p>بسم الله الرحمن الرحيم<br>اللَّهُمَّ صَلِّ عَلَى مُحَمَّدٍ وَعَلَى آلِ مُحَمَّدٍ</p><p>Hey everyone! I’m Prizmo, and today I’m going to share an interesting vulnerability I came across during one of my recent assessments.<br>The target was a collaboration platform that allows users to create teams, add members, and manage shared boards.</p><p>During my exploration, I identified an issue where the platform unintentionally exposes <strong>sensitive user information</strong> belonging to users who were removed from a team. Even though the frontend hides this data.</p><p><strong>Let`s get started</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fn69AaUSkbu8RVVuz24%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FThisIsMashed-animation-animated-mashed-n69AaUSkbu8RVVuz24&amp;image=https%3A%2F%2Fmedia4.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExemQ3ZjlxbXE4M3hkZWN2aXZteTF4OXV5cXo2aW54aXd6OTcwMnUyeCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2Fn69AaUSkbu8RVVuz24%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/142e3844feb8396fe4b1879d1077d12a/href">https://medium.com/media/142e3844feb8396fe4b1879d1077d12a/href</a></iframe><p><strong>How i discovered the bug</strong></p><p>I started by exploring the platform to understand how it works and how users interact with it. I quickly noticed that the site has a <strong>Teams system</strong>, allowing users to create teams, invite members, and collaborate within shared boards.</p><p>To test this, I created <strong>two accounts</strong> on the platform:</p><ul><li><strong>Account A</strong></li><li><strong>Account B</strong></li></ul><p>Using Account A, I sent an invitation to Account B. After accepting the invitation, Account B appeared in <strong>two places</strong> in Account A’s interface:</p><ol><li><strong>My Contacts</strong></li><li><strong>My Team</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GWnA7egea-ZTRgSfl4bjuA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*HUZceLwEdMZtugb2r5Lu6w.png" /></figure><p>Next, I removed Account B from the team. I noticed that while Account B <strong>disappeared from “My Team”</strong>, it was still listed in <strong>“My Contacts”</strong>. However, the email field now displayed:</p><blockquote><em>“Email hidden — ONLY MEMBERS OF THE TEAM CAN SEE EACH OTHER EMAIL”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*9FhYvO2MdFvG9r2xap251Q.png" /></figure><p>At that point, I started thinking, <em>what if the email is only hidden in the UI, but the backend API is still returning the user’s data?</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fa5viI92PAF89q%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Freaction-a5viI92PAF89q&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExOGpyenhlY2pranBtNHZjdGJtdzNyZXNyZXBhYWxpNXczZWQzbXVyNiZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2Fa5viI92PAF89q%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="300" frameborder="0" scrolling="no"><a href="https://medium.com/media/96e3562d06a2a3a06d45ee1aed677f2a/href">https://medium.com/media/96e3562d06a2a3a06d45ee1aed677f2a/href</a></iframe><p>After that, I went to Burp Suite, opened the burp history, and started looking through the request history. I found the request that returns the <strong>contacts</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*huY2Nbt_Q0gM0jkBwu4KNA.png" /></figure><p>I sent this request to the repeater and clicked send to my surprise , I found that the data was actually <strong>leaking through the API</strong>, showing the user’s email and ID even though they were supposed to be hidden.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*mmVc5dUWnR1ysBq7RGRykQ.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F10UeedrT5MIfPG%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fdancing-happy-cartoons-10UeedrT5MIfPG&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExa29pdWg1MWYzNjFvM3p6OHU2bXFiOG90OW10ajF6dGNpbjZ5NHc3dCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F10UeedrT5MIfPG%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="318" frameborder="0" scrolling="no"><a href="https://medium.com/media/6dd4ced26d74ce2247db3429cd3eacec/href">https://medium.com/media/6dd4ced26d74ce2247db3429cd3eacec/href</a></iframe><p>To further confirm, I took an extra step: I logged into <strong>Account B</strong> and changed its email address. Then I sent the same API request again, and sure enough — the response now included <strong>Account B’s updated email and user ID</strong>.</p><p>After discovering the issue, I <strong>reported the bug</strong> to the platform. The report was accepted, and was <strong>awarded with bounty</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CnyIbBxvWo7aCENVMysphQ.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F67ThRZlYBvibtdF9JH%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Flooneytunes-looney-tunes-bugs-bunny-pay-day-67ThRZlYBvibtdF9JH&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExYzF5N2Y5aGdxZ3FiOGc3NWE5NGNlM3k5ajZ6aHkxem5ka3EzeTBycyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F67ThRZlYBvibtdF9JH%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/a487f19908c9eecdeb3d166123f3e9ef/href">https://medium.com/media/a487f19908c9eecdeb3d166123f3e9ef/href</a></iframe><p>If you’ve made it this far, <strong>thank you for reading,</strong> I hope you found this write-up insightful and learned something useful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c0b43bded77" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>