<?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 Naka on Medium]]></title>
        <description><![CDATA[Stories by Naka on Medium]]></description>
        <link>https://medium.com/@nakah_?source=rss-ad8f97265e12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MGfrrL09MeX82RRW0-GTZw.png</url>
            <title>Stories by Naka on Medium</title>
            <link>https://medium.com/@nakah_?source=rss-ad8f97265e12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:01:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nakah_/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[Pluck CMS Stored XSS in Page Editor (CVE-2026–31205)]]></title>
            <link>https://medium.com/@nakah_/pluck-cms-stored-xss-in-page-editor-cve-2026-31205-3b0526743e1d?source=rss-ad8f97265e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b0526743e1d</guid>
            <dc:creator><![CDATA[Naka]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 19:15:53 GMT</pubDate>
            <atom:updated>2026-04-30T19:15:53.017Z</atom:updated>
            <content:encoded><![CDATA[<p>While testing Pluck CMS, I identified a stored Cross-Site Scripting (XSS) vulnerability in the page editor functionality affecting versions prior to 4.7.21-dev. The issue allows authenticated users to inject arbitrary JavaScript into page content, which is then executed when the page is viewed.</p><p>Although this requires access to the admin panel, the vulnerability is still impactful, as it enables persistent client-side code execution within the application.</p><h3>Where the Issue Lives</h3><p>The vulnerability is triggered through the page editing feature:</p><blockquote>admin.php?action=editpage</blockquote><p>When editing or creating a first page, user input is sent via the cont2 parameter, which represents the page content. This input is processed by the sanitizePageContent() function located in:</p><blockquote>data/inc/functions.all.php</blockquote><p>At first glance, the application attempts to sanitize user input. However, the filtering is not strict enough to prevent malicious payloads from being stored and later rendered.</p><h3>Root Cause</h3><p>The core issue is improper sanitization of user-controlled HTML content.</p><p>The sanitizePageContent() function does not fully neutralize dangerous input. In practice, this means:</p><ul><li>Malicious JavaScript can be injected into page content</li><li>Certain HTML tags or attributes are not properly filtered</li><li>Output is rendered without sufficient encoding</li></ul><p>Because of this, attacker-controlled input is stored directly in the application and executed in the browser when the page is accessed.</p><h3>Proof of Concept</h3><p>The vulnerability can be reproduced with the following steps:</p><p>Start by navigating to the page editor:</p><p>admin.php?action=editpage</p><p>Create the<strong> first page</strong> and insert a malicious JavaScript payload into the content field (cont2). When the form is submitted, the application processes the input using the sanitizePageContent() function.</p><p>Due to insufficient filtering, the payload is stored without being properly sanitized.</p><p>Next, visit the newly created page. At this point, the injected JavaScript executes in the browser, confirming the presence of a stored XSS vulnerability.</p><p>Interestingly, if the same page is edited again, a different sanitization function is applied. This may result in the payload being removed or altered, highlighting that the issue specifically affects the initial page creation process.</p><p>Since the payload is stored, it executes every time the page is viewed.</p><p>A simple example would be injecting a script that executes when the page loads, demonstrating full control over the client-side context.</p><h3>Impact</h3><p>This is a classic stored XSS scenario with persistent execution. The impact includes:</p><ul><li>Execution of arbitrary JavaScript in users’ browsers</li><li>Session hijacking (depending on cookie protections)</li><li>Unauthorized actions performed on behalf of authenticated users</li><li>Content manipulation or defacement</li></ul><p>Even in cases where only administrators can access the editor, this type of vulnerability can still be abused in shared environments or chained with other issues.</p><h3>Fix and Mitigation</h3><p>The issue has been addressed in version 4.7.21-dev.</p><p>To properly mitigate this class of vulnerability, applications should:</p><ul><li>Apply strict allowlist-based sanitization for HTML input</li><li>Encode output before rendering it in the browser</li><li>Avoid trusting user-supplied content, even from authenticated users</li><li>Consider deploying a Content Security Policy (CSP) as a defense-in-depth measure</li></ul><h3>References</h3><ul><li><a href="https://github.com/pluck-cms/pluck/blob/main/data/inc/functions.all.php#L207">https://github.com/pluck-cms/pluck/blob/main/data/inc/functions.all.php#L207</a></li><li><a href="https://github.com/pluck-cms/pluck/blob/main/data/inc/editpage.php">https://github.com/pluck-cms/pluck/blob/main/data/inc/editpage.php</a></li><li><a href="https://github.com/pluck-cms/pluck/issues/141">https://github.com/pluck-cms/pluck/issues/141</a></li></ul><h3>Disclosure</h3><p>This issue is tracked as CVE-2026–31205 and has been acknowledged by the vendor.</p><h3>Credits</h3><p>Discovered by Naka.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b0526743e1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CVE-2025–56571 and CVE-2025–56572: Denial of Service Vulnerabilities in Finance.js]]></title>
            <link>https://medium.com/@nakah_/cve-2025-56571-and-cve-2025-56572-denial-of-service-vulnerabilities-in-finance-js-78f8b399f53b?source=rss-ad8f97265e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/78f8b399f53b</guid>
            <dc:creator><![CDATA[Naka]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 06:44:10 GMT</pubDate>
            <atom:updated>2025-09-28T04:20:45.373Z</atom:updated>
            <content:encoded><![CDATA[<h3>Summary</h3><p>Two Denial of Service (DoS) vulnerabilities were identified in Finance.js version 4.1.0, affecting its IRR and seekZero() functions. Both vulnerabilities can cause excessive CPU usage and application crashes under certain input conditions.</p><h3>Description</h3><ul><li>CVE-2025–56571:<br>The IRR function in Finance.js v4.1.0 does not properly limit recursion or iteration depth, which may lead to excessive CPU consumption and application stalls or crashes.</li><li>CVE-2025–56572:<br>The seekZero() function in Finance.js v4.1.0 lacks iteration limits, potentially leading to infinite loops, high CPU usage, and application crashes in both browser and Node.js environments.</li></ul><p>Both CVE-2025–56571 and CVE-2025–56572 share the same high CVSS v3.1 score of 7.5 due to remote, no-privilege denial-of-service impact on availability only.</p><p>AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H</p><h3>Affected Software</h3><p>Finance.js version 4.1.0</p><h3>Disclosure Status</h3><p>This CVE entry is currently in a RESERVED state with the MITRE CVE Team. This public reference is created to fulfill the minimum disclosure requirements for the vulnerability publication process.</p><h3>References</h3><ul><li><a href="https://github.com/ebradyjobory/finance.js">https://github.com/ebradyjobory/finance.js</a></li><li><a href="https://raw.githack.com/ebradyjobory/finance.js/6d571ea2a86d08491ceb584e292e9b76b0a60636/finance.js">https://raw.githack.com/ebradyjobory/finance.js/6d571ea2a86d08491ceb584e292e9b76b0a60636/finance.js</a></li></ul><h3>Credit</h3><p>Reported by Naka</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78f8b399f53b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recommended Design for a Secure Network Architecture]]></title>
            <link>https://medium.com/@nakah_/recommended-design-for-a-secure-network-architecture-15612e17ece4?source=rss-ad8f97265e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/15612e17ece4</guid>
            <category><![CDATA[network]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[hacker]]></category>
            <dc:creator><![CDATA[Naka]]></dc:creator>
            <pubDate>Sat, 25 Feb 2023 19:43:46 GMT</pubDate>
            <atom:updated>2023-02-25T19:43:46.215Z</atom:updated>
            <content:encoded><![CDATA[<p>In this writeup, I will be discussing a new topic focusing on network security and specifically a “recommended” network architecture. Before diving into the details, it’s important to understand what a network diagram is.</p><p>A network diagram is a visual representation of a network’s structure, which includes various components such as routers, firewalls, switches, servers, and other network devices. The diagram provides a high-level overview of the network’s design and helps in identifying potential vulnerabilities and threats. A well-designed network architecture is critical for ensuring a secure and reliable network infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZlvrBongis9gtUIGB8VF9A.png" /></figure><p>The network diagram provided in this scenario follows a commonly used architecture that employs multiple layers of security mechanisms to safeguard an organization’s network and data from external threats. The diagram shows that the network architecture incorporates three firewalls, each with a specific function. The first firewall is responsible for filtering and blocking potentially harmful traffic from the internet before it can reach the organization’s internal network. The second firewall is located in the DMZ and monitors and controls traffic to and from the DMZ, which isolates public-facing servers from the internal network. The third firewall helps to control and monitor traffic between the internal network and the servers, and can be configured to block any potentially malicious traffic that may have bypassed the external firewall or the firewall with ADS.</p><p>In addition to the firewalls, the network architecture includes switches, honeypots, VLANs, and access points. The switches segregate network traffic between the internal network and the DMZ, and VLANs further segment the network to ensure proper traffic control. The honeypot system lures potential attackers and gathers information about their methods and techniques, while access points provide wireless connectivity while ensuring wireless traffic protection.</p><p>It’s crucial to note that while this network security architecture provides multiple layers of security, it is not a one-size-fits-all design. Each organization’s network security requirements are unique, and a comprehensive risk assessment and analysis are necessary to identify potential threats and vulnerabilities and develop a custom network security architecture that best meets an organization’s specific needs and requirements. By following this approach, organizations can effectively protect their network and data from external threats and reduce the risk of a successful cyberattack.</p><p>I hope that this information was clear and helpful. Thank you for reading.</p><p><em>Feedback, suggestions and your point of view are always appreciated!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15612e17ece4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An amazing way to turn a xss into an ATO]]></title>
            <link>https://medium.com/@nakah_/an-amazing-way-to-turn-a-xss-into-an-ato-40bc92772195?source=rss-ad8f97265e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/40bc92772195</guid>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[account-takeover-attacks]]></category>
            <category><![CDATA[xss-vulnerability]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Naka]]></dc:creator>
            <pubDate>Mon, 02 Jan 2023 17:01:45 GMT</pubDate>
            <atom:updated>2023-01-02T17:01:45.117Z</atom:updated>
            <content:encoded><![CDATA[<p>In this write-up, I will discuss a bug that both myself and Flag_c0 discovered in a program. Without further delay, let’s get into the details of the vulnerability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MTQrdnpF2yy0UtQOTWH8Yw.jpeg" /></figure><h4>Finding the xss</h4><p>Flag_c0 found an XSS vulnerability while browsing the website. He discovered a hidden parameter that allowed them to bypass a simple filter by changing `<em>&lt;script&gt;</em>` to `<em>&lt;ScRiPt&gt;</em>`, leading to the XSS vulnerability. This vulnerability was easy to find, which is why it was marked as a duplicate.</p><h4>Account Takeover</h4><p>To escalate this issue, Flag_c0 found that the CSRF token was being reflected on the source code in the profile settings when visited. This meant that if we were able to obtain the CSRF token, we could use JavaScript to change the email and profile settings.</p><p>However, we encountered difficulties while attempting to fetch the settings because the filter was blocking certain words , so I had the idea to use an external JavaScript file, <em>&lt;script src=”my_js.file”&gt;</em>, to make it easier to fetch the settings since it would allow me to escape the filters.</p><p>Now that the difficult part is completed, we just need to extract the CSRF token and send a POST request to update the email and country in the profile settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*k_kETpCzqIU7pYDwsMLdhA.png" /></figure><p>This code defines two functions: `<em>changeEmail</em>` and `<em>handleResponse</em>`. `<em>ChangeEmail</em>` sends an HTTP GET request to `<em>/xx/profile/edit</em>`, and when the response is received, it calls the `handleResponse` function.</p><p>The `<em>handleResponse</em>` function extracts the CSRF token from the response text and then sends an HTTP POST request to `<em>/xx/profile/update</em>` with the necessary headers and request body to update the email address and country in the profile settings.</p><p>I hope that this information was clear and helpful. Thank you for reading.</p><p><em>Feedback, suggestions and your point of view are always appreciated!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40bc92772195" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How and why should you collaborate in bug bounty programs]]></title>
            <link>https://medium.com/@nakah_/how-and-why-you-should-collaborate-in-bug-bounty-95d804a7fb48?source=rss-ad8f97265e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/95d804a7fb48</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hackin]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[bug-bounty-tips]]></category>
            <dc:creator><![CDATA[Naka]]></dc:creator>
            <pubDate>Sun, 04 Dec 2022 00:32:37 GMT</pubDate>
            <atom:updated>2023-01-02T14:57:59.684Z</atom:updated>
            <content:encoded><![CDATA[<p>In this write-up, I will discuss collaboration in bug bounty programs. I have received many questions about this topic, so I thought it would be a good idea to address it.</p><p>Collaboration in bug bounty programs is a crucial aspect of identifying and addressing vulnerabilities in a company’s security systems. By working together, individuals and teams can bring a wider range of perspectives and expertise to bear on the problem, increasing the chances of identifying and resolving potential vulnerabilities. This collaboration often takes place within online forums or platforms specifically designed for bug bounty programs.</p><p>In addition to the benefits of collaboration in terms of efficiency and resource utilization, collaboration in bug bounty programs can also be a valuable source of knowledge sharing and skill development. By working together and sharing their expertise, hackers can learn from each other’s skills and experiences, gaining new insights and perspectives on how to identify and report vulnerabilities. This can be especially valuable for less experienced hackers, who can benefit from the guidance and support of more experienced collaborators.</p><h4>If you want to collaborate with a friend in a bug bounty program, here are some steps you can follow:</h4><p>1. <strong>Reach out to your friend</strong> and let them know that you want to work together on a bug bounty. You can do this over email, a messaging app, or in person.</p><p>2.<strong>Decide on a target</strong>. This could be a specific website or application that you both want to focus on, or it could be a broader category of targets (e.g. online shopping sites).</p><p>3. <strong>Plan your approach</strong>. Talk to your friend about the types of vulnerabilities you both want to look for, and come up with a plan for how you will divide the work and share findings.<br> <br>4. <strong>Start hunting for bugs.</strong> Work together to scan the target for vulnerabilities, and use your knowledge and skills to identify potential issues.</p><p>5.<strong> Share findings</strong>. As you find vulnerabilities, share them with your friend so that you can both work on reproducing and verifying the issue.</p><p>6. <strong>Submit your findings.</strong> Once you have verified a vulnerability, submit it to the bug bounty program using the program’s submission guidelines. Be sure to include any information that will help the program verify your findings, such as detailed steps for reproducing the issue.</p><blockquote>By following these steps, you can collaborate with a friend in a bug bounty program and make the most of your combined skills and knowledge.</blockquote><p>In conclusion, collaboration in bug bounty programs is essential for identifying and addressing vulnerabilities in a company’s security systems. Working together allows individuals and teams to bring a wider range of perspectives and expertise to bear on the problem, increasing the chances of identifying and resolving potential vulnerabilities. Collaboration can also be a valuable source of knowledge sharing and skill development, fostering a sense of community among participating hackers.</p><p>In the future, I am planning to write a write-up about my collaboration in a bug bounty program with some hackers. I will share everything I have learned and discovered in that write-up.</p><p><em>Feedback, suggestions and your point of view are always appreciated!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95d804a7fb48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned from reading 150 Account Takeover writeups]]></title>
            <link>https://medium.com/@nakah_/what-i-learned-from-reading-150-account-takeover-writeups-7589fae9fbc3?source=rss-ad8f97265e12------2</link>
            <guid isPermaLink="false">https://medium.com/p/7589fae9fbc3</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Naka]]></dc:creator>
            <pubDate>Wed, 02 Nov 2022 11:02:01 GMT</pubDate>
            <atom:updated>2022-11-02T21:54:24.392Z</atom:updated>
            <content:encoded><![CDATA[<h3>What I learned from reading 150 account takeover writeups</h3><p>In this article, we will discuss what I learned by reading 150 write-ups about Account Takeover attacks.</p><p><strong>What is an account takeover?</strong></p><p>Account takeover (ATO) Is a method to obtain unauthorized access to someone else’s account. In most cases, this is a High/Critical vulnerability (P2/P1).</p><p><strong>In which ways are ATOs performed?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JDXnJJa_v1fw8UfPaXBBDw.png" /></figure><ul><li>XSS 26.8%</li><li>IDOR 13.2%</li><li>Server Misconfiguration 12.4%</li><li>Flaws in Reset/Forgotten Password Functionality 12.4%</li><li>Open Redirect 7.9%</li><li>CSRF 7.1%</li><li>Oauth/2FA Flaws 7.1%</li><li>ETC</li></ul><p><strong>Cross-Site Script (XSS)</strong></p><p>Before reading the writeups I expected XSS to be the most common, since you can inject JavaScript code and easily extract sensitive information and cookies.</p><p><strong>Here are some of the possible vulnerabilities:</strong></p><p>- Is the website using <strong>httponly</strong> cookies? <a href="https://mohamedtarekq.medium.com/defeat-the-httponly-flag-to-achieve-account-takeover-rxss-c16849d3d192">Source</a>, <a href="https://www.r29k.com/articles/bb/priv-esc-via-stored-xss">Source</a></p><p>- Sometimes it can be found in LocalStorage. <a href="https://medium.com/@gguzelkokar.mdbf15/xss-via-account-takeover-in-e-signature-feature-worth-2500-435f3f8325bf">Source</a></p><p>- Or in IndexedDB. <a href="https://infosecwriteups.com/stored-xss-to-account-takeover-going-beyond-document-cookie-970e42362f43">Source</a></p><p>- Is it a self XSS? Maybe you can chain it with another bugs. <a href="https://ysamm.com/?p=763">Source</a>, <a href="https://gonzx.medium.com/how-i-escalate-my-self-stored-xss-to-account-takeover-with-the-help-of-idor-f20733ecdbe9">Source</a>, <a href="https://medium.com/@behnam.yazdanpanah/chaining-bugs-from-self-xss-to-account-takeover-82d572136bdf">Source</a>, <a href="https://medium.com/@renwa/the-underrated-bugs-clickjacking-css-injection-drag-drop-xss-cookie-bomb-login-logout-csrf-84307a98fffa">Source</a></p><p>- Cookie based XSS? <a href="https://medium.com/@moSec/crlf-to-account-takeover-chaining-bugs-21a25dfa1cdf">Source</a>, <a href="https://bergee.it/blog/turning-cookie-based-xss-into-account-takeover/">Source</a></p><p>By reading these write-ups, I found out that there are several methods to turn a simple xss into an impactful account takeover and increase the severity of the vulnerability from P4/P3 to P1.</p><p><strong>IDOR</strong></p><p>Insecure Direct Object Reference (IDOR), which occurs when an application exposes a reference to an internal implementation object. In English 😅, it is when a part of an application allows you to request and receive information that you’re not authorized to see.</p><ul><li>I noticed that 50% if the IDORs are disclosing PII information <a href="https://medium.com/@ryuukhagetsu/how-i-get-bounty-from-takeover-account-ed17cd838b2a">Source</a>, <a href="https://medium.com/@kojodaprogrammer/full-account-takeover-ato-a-tale-of-two-bugs-d1b3765ff1de">Source</a>, <a href="https://medium.com/@tobydavenn/how-i-was-able-to-takeover-any-account-on-one-of-europes-largest-media-companies-e8d25e59c08">Source</a>, <a href="https://medium.com/pentesternepal/a-tale-of-zero-click-account-takeover-56b51fdbd7ae">Source</a>, <a href="https://tox7cv3nom.github.io/2021/11/12/chaining-of-csrf-token-misconfiguration-and-no-rate-limit-leads-to-mass-account-takeover.html">Source</a></li><li>30% editing/changing the victim account <a href="https://ahmadaabdulla.medium.com/vulnerabilitymultiple-vulnerability-leading-to-account-takeover-in-tiktok-smb-subdomain-c99e4a50b377">Source</a>, <a href="https://medium.com/@sazouki/how-i-hacked-one-of-the-biggest-airline-in-the-world-e7810dc43791">Source</a>, <a href="https://m7arm4n.medium.com/zero-click-to-account-takeover-d764e12bee4b">Source</a></li><li>And 20% Broken Access <a href="https://infosecwriteups.com/massive-users-account-takeovers-chaining-vulnerabilities-to-idor-ea4e1b6407d2">Source</a>, <a href="https://web.archive.org/web/20220513145411/">Source</a>, <a href="https://pwnsec.ninja/2022/05/12/takeover-seller-accounts-worth-billions-millions/">Source</a></li></ul><p><strong>Flaws in Reset/Forgotten Password Functionality</strong></p><p>This was the vulnerability that surprised me the most, as I had not expected that this feature could be so vulnerable. The bugs on this functionality are :</p><ul><li>53.4%IDORs (These IDORs are included in the 30% editing/change the victim account )</li><li>46.6% Misconfigurations on the Functionality</li></ul><p>Some IDORs allow the attacker to change the password of the victim account. <a href="https://medium.com/@noob.assassin/5k-misconfigured-reset-password-that-leads-to-account-takeover-no-user-interaction-ato-e6a36b8ef183">Source</a>, <a href="https://infosecwriteups.com/account-takeover-user-admin-via-password-reset-322b8020ea6">Source</a>, <a href="https://infosecwriteups.com/my-fourth-account-takeover-through-password-reset-28a36dfebaf">Source</a>, <a href="https://akashhamal0x01.medium.com/watch-out-the-links-account-takeover-32b9315390a7">Source</a></p><p>In the case of the misconfigurations, they usually allow the attacker normally allows the attacker to change the password of the victim even without access to the account. For e.g.</p><p>— The attacker is able to change the password of the users if they remove the token for the request. <a href="https://tarekbouali.com/posts/how-i-hacked-one-of-the-biggest-airlines-group-of-the-world/">Source</a><br> — Request the change for 2 emails separating them with a comma or semicolon. <a href="https://infosecwriteups.com/a-tale-of-0-click-account-takeover-and-2fa-bypass-b369cd70e42f">Source</a><br> — Lack of token validation. <a href="https://0xmahmoudjo0.medium.com/admin-account-takeover-via-weird-password-reset-functionality-166ce90b1e58">Source</a></p><p><strong>Open Redirect</strong></p><p><strong>What an Open Redirect is?</strong></p><p>Open redirection vulnerabilities arise when an application incorporates user-controllable data into the target of a redirection in an unsafe way.</p><p>The account takeovers via open redirect happen due to improper input validation which leads to tokens being leaked:<br>- In most of the cases OAuth. <a href="https://www.bugbounty.info/2022/08/never-underestimate-power-of-open.html">Source</a>, <a href="https://ysamm.com/?p=697">Source</a>, <a href="https://medium.com/@vflexo/full-account-takeover-via-open-redirection-41c167db46">Source</a></p><p><strong>CSRF</strong></p><p>Cross-Site Request Forgery (CSRF) is an attack that forces an end user to perform unwanted actions on a web application in which they’re currently authenticated.</p><p>While reading the write-ups, I realized that this vulnerability can be used without chaining other bugs but most of the time it is used to escalate XSS.</p><ul><li>62.5% — Chain XSS to get ATO. <a href="https://ahmadaabdulla.medium.com/vulnerabilitymultiple-vulnerability-leading-to-account-takeover-in-tiktok-smb-subdomain-c99e4a50b377">Source</a>, <a href="https://ysamm.com/?p=763">Source</a>, <a href="https://medium.com/@renwa/the-underrated-bugs-clickjacking-css-injection-drag-drop-xss-cookie-bomb-login-logout-csrf-84307a98fffa">Source</a>, <a href="https://medium.com/@behnam.yazdanpanah/chaining-bugs-from-self-xss-to-account-takeover-82d572136bdf">Source</a></li><li>37.5% — Change The user Setting using CSRF. <a href="https://bloggerrando.blogspot.com/2022/08/17-1.html">Source</a>, <a href="https://bloggerrando.blogspot.com/2022/08/17-1.html">Source</a>, <a href="https://webs3c.com/t/csrf-leads-to-account-takeover-in-yahoo/93">Source</a>, <a href="https://infosecwriteups.com/bug-hunting-journey-of-2021-1fa60b28d949">Source</a></li></ul><p><strong>2FA/OAuth</strong></p><p>Even though these two functionalities are different, they can be exploited in a similar way. For exemple:</p><ul><li>Broken Access/Bypassing Authentication. <a href="https://infosecwriteups.com/account-takeover-worth-1000-611452063cf">Source</a>, <a href="https://medium.com/@bughunt789/account-takeover-via-response-manipulation-96be568feb7e">Source</a>, <a href="https://infosecwriteups.com/a-tale-of-0-click-account-takeover-and-2fa-bypass-b369cd70e42f">Source</a>, <a href="https://medium.com/@anjaneyulukanakatla1996/its-all-about-2fa-bypass-or-account-takeover-f9521f0a03b5">Source</a></li></ul><p><strong>Summary/Key takeaways</strong></p><ul><li>26.8% of ATOs are escalated from XSS.</li><li>Always try to get a bigger impact out of XSS attacks.</li><li>Success in finding ATOs comes from <em>creative ways</em> of exploiting them.</li><li>Even the biggest companies are vulnerable to this kind of bugs.</li></ul><p>This is my first writeup here :) and it would not be possible without <a href="https://medium.com/@nynan">@nynan</a>’s help, hope you enjoy it!</p><p><em>Feedback, suggestions and your point of view are always appreciated!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7589fae9fbc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>