LetsExchange Web & API & Widget: Swap, Bridge, DEX

Bug bounty Triaged by HackenProof LetsExchange Web & API & Widget: Swap, Bridge, DEX: Program info LetsExchange Web & API & Widget: Swap, Bridge, DEX Company: LetsExchange Scope Review: 311952 Submissions: 144 Total rewards: $2,720 Reputation 100 points required PoC Required Program left: 30 days ago Finished Submit report Contest is not active Program info Hackers 88 Reports 0 LetsExchange offers users an instant cryptocurrency swap service with the widest range of supported cryptocurrencies on the market. Users can exchange crypto quickly and easily. Additionally, users can buy and sell crypto for fiat using credit cards, and take advantage of DEX and cross-chain bridge functionalities. The platform prioritizes convenience, security, and efficiency, ensuring a hassle-free experience for all users. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Previous reports Scope Search targets In scope Target │ Type │ Severity https://letsexchange.io/ Copy The LetsExchange.io website is the gateway to our cryptocurrency exchange services, providing users with access to features like instant swaps, a crypto bridge, and API integrations. The website is designed to deliver a seamless, secure, and intuitive experience for users across the globe. Researchers are invited to assess potential vulnerabilities in the website, including security flaws, improper handling of user data, cross-site scripting (XSS), or other issues that could compromise the platform's integrity or user trust. │ Web │ Critical https://api.letsexchange.io/ Copy LetsExchange.io's API is a powerful tool designed to integrate cryptocurrency exchange functionality into external platforms, such as wallets, aggregators, and other B2B solutions. This target focuses on ensuring the API's security, stability, and flawless operation in facilitating fast, efficient, and user-friendly crypto swaps. The API processes requests for exchanging over 3,000 cryptocurrencies, supports various workflows, and ensures high reliability and uptime for partner integrations. Researchers are encouraged to identify potential vulnerabilities, including improper handling of requests, unauthorized data access, or issues affecting integration performance. │ API │ Critical https://letsexchange.io/?mode=bridge Copy LetsExchange.io's Bridge is a centralized solution designed to facilitate seamless cross-chain operations for cryptocurrencies available on multiple networks. This feature leverages the platform’s core processing infrastructure to enable users to swap the same cryptocurrency between different blockchain networks quickly and efficiently. Researchers are encouraged to focus on potential vulnerabilities in the bridge's functionality. │ Bridge │ Critical https://letsexchange.io/swap Copy LetsExchange.io's Swap mode, integrated into our widget, offers users a seamless and instant cryptocurrency exchange experience. Supporting over 5,000+ coins and tokens across multiple blockchain networks, this feature ensures hassle-free swaps. Researchers are invited to explore potential vulnerabilities in the Swap mode, such as transaction inaccuracies, data leakage, unauthorized access, or issues affecting the user experience. The focus is on identifying risks that could impact the security, stability, or reliability of the exchange process. │ Web │ Critical Focus Area IN-SCOPE VULNERABILITIES (WEB) We are interested in the following vulnerabilities: Business logic issues Payments manipulation Remote code execution (RCE) Injection vulnerabilities (SQL, XXE) File inclusions (Local & Remote) Access Control Issues (IDOR, Privilege Escalation, etc) Leakage of sensitive information Server-Side Request Forgery (SSRF) Cross-Site Request Forgery (CSRF) Cross-Site Scripting (XSS) Directory traversal Other vulnerability with a clear potential loss OUT OF SCOPE: WEB VULNERABILITIES Vulnerabilities found in out of scope resources are unlikely to be rewarded unless they present a serious business risk (at our sole discretion). In general, the following vulnerabilities do not correspond to the severity threshold: Vulnerabilities in third-party applications Assets that do not belong to the company Best practices concerns Recently (less than 30 days) disclosed 0day vulnerabilities Vulnerabilities affecting users of outdated browsers or platforms Social engineering, phishing, physical, or other fraud activities Publicly accessible login panels without proof of exploitation Reports that state that software is out of date/vulnerable without a proof of concept Reports that generated by scanners or any automated or active exploit tools Vulnerabilities involving active content such as web browser add-ons Most brute-forcing issues without clear impact Denial of service (DoS/DDoS) Theoretical issues Moderately Sensitive Information Disclosure Spam (sms, email, etc) Missing HTTP security headers Infrastructure vulnerabilities, including: Certificates/TLS/SSL-related issues; DNS issues (i.e. MX records, SPF records, DMARC records etc.); Server configuration issues (i.e., open ports, TLS, etc.) Open redirects Session fixation User account enumeration Clickjacking/Tapjacking and issues only exploitable through clickjacking/tap jacking Descriptive error messages (e.g. Stack Traces, application or server errors) Self-XSS that cannot be used to exploit other users Login & Logout CSRF Weak Captcha/Captcha Bypass Lack of Secure and HTTPOnly cookie flags Username/email enumeration via Login/Forgot Password Page error messages CSRF in forms that are available to anonymous users (e.g. the contact form) OPTIONS/TRACE HTTP method enabled Host header issues without proof-of-concept demonstrating the vulnerability Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS Content Spoofing without embedded links/HTML Reflected File Download (RFD) Mixed HTTP Content HTTPS Mixed Content Scripts Manipulation with Password Reset Token MitM and local attacks OUT OF SCOPE: MOBILE VULNERABILITIES Attacks requiring physical access to a user's device Vulnerabilities that require root/jailbreak Vulnerabilities requiring extensive user interaction Exposure of non-sensitive data on the device Reports from static analysis of the binary without PoC that impacts business logic Lack of obfuscation/binary protection/root(jailbreak) detection Bypass certificate pinning on rooted devices ​Lack of Exploit mitigations i.e., PIE, ARC, or Stack anaries Sensitive data in URLs/request bodies when protected by TLS Path disclosure in the binary OAuth & app secret hard-coded/recoverable in IPA, APK Sensitive information retained as plaintext in the device’s memory Crashes due to malformed URL Schemes or Intents sent to exported Activity/Service/Broadcast Receiver (exploiting these for sensitive data leakage is commonly in scope) Any kind of sensitive data stored in-app private directory Runtime hacking exploits using tools like but not limited to Frida/ Appmon (exploits only possible in a jailbroken environment) Shared links leaked through the system clipboard Any URIs leaked because a malicious app has permission to view URIs opened. Exposure of API keys with no security impact (Google Maps API keys etc.) Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic Make every effort not to damage or restrict the availability of products, services, or infrastructure Avoid compromising any personal data, interruption, or degradation of any service Don’t access or modify other user data, localize all tests to your accounts Perform testing only within the scope Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam Don’t spam forms or account creation flows using automated scanners In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity. Don’t break any law and stay in the defined scope Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission Eligibility and Coordinated Disclosure We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward: You must be the first reporter of a vulnerability. The vulnerability must be a qualifying vulnerability Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary. You must not be a former or current employee of us or one of its contractor. ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded) Provide detailed but to-the point reproduction steps Disclosure Guidelines Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization No vulnerability disclosure, including partial is allowed for the moment. Please do NOT publish/discuss bugs Previous reports HackenProof - 2023 HackenProof - 2024 Live since 23 Jun 2023 Published date 23 Jun 2023 Last updated 20 Oct 2026 Range of bounty $100 - $2,000 Severity Critical $1,000 - $2,000 High $500 - $1,000 Medium $200 - $500 Low $100 - $200 CEX Web @Letsexchange-scammed-me Verified 1 @cats-are-aliens Verified 2 @f12enjoy3r Verified 3 pi @pietrovari 4 @Abhiram KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d