Cetus Web

Bug bounty Triaged by HackenProof Cetus Web: Program info Cetus Web Company: Cetus Scope Review: 323776 Submissions: 184 Total rewards: $2,670 Reputation 100 points required PoC Required Program is: active now Live Submit report Program info Hackers 82 Reports 0 Cetus is a pioneer DEX and concentrated liquidity protocol built on the Sui network. The mission of Cetus is building a powerful and flexible underlying liquidity network to make trading easier for any users and assets. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://app.cetus.zone Copy Web │ Critical *.cetus.zone Copy Web │ Medium Focus Area IN SCOPE VULNERABILITIES: WEB, MOBILE 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 vulnerabilities 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 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/tapjacking 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 clear security impact 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 Response manipulations without demonstration of system state change Moderately Sensitive Information Disclosure (e.g., non-sensitive logs or generic error stack traces without personal data or credentials) 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 AI-generated proof-of-concepts (PoCs) that do not include detailed architectural context and clear steps to demonstrate real impact may not qualify for a bounty. Submitting repeated low-quality or duplicate reports, or spamming the program with findings that do not meet the scope or quality standards, may result in disqualification from receiving any rewards. 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 the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded) Provide detailed but to-the point reproduction steps Estimated bounty ranges will depend on severity, impact, and quality of the report AI-generated reports without runable PoC are not accepted under this program. 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. Platform-Only Disclosure: Disclosure is only possible through the HackenProof Disclosure function. Researchers may request disclosure (Limited or Full) within the report ticket; We reserve the right to approve, redact, or deny disclosure requests at our sole discretion. Mutual Required: Any publication requires explicit mutual agreement. Reports must remain Private until the status is officially changed to "Public" on the HackenProof platform by the team. Live since 08 Apr 2026 Published date 08 Apr 2026 Last updated 06 Jul 2026 Range of bounty $10 - $10,000 Severity Critical $5,000 - $10,000 High $1,000 - $5,000 Medium $100 - $1,000 Low $10 - $100 dApp DEX Sui Ecosystem Web apps SUI @rathvahet KYC Verified 1 @itzdaglitch KYC Verified 2 @Holl0w KYC Verified 3 @ashrafalani91 Verified 4 @FarhanNoufandaHusain KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d