CodeVulnHunt - Contact & Contributions

Welcome to the CodeVulnHunt GitHub repository! This repository is meant to help users reach out to the CodeVulnHunt team, report issues with the platform, or submit new challenges that we can feature on the website.

📬 Contact Us

If you have any questions, feedback, or need assistance, feel free to contact us by opening a new issue. Here’s how you can get in touch:

1. Open a New Issue:
   • Navigate to the Issues tab.
   • Click on New Issue.
   • In the title, briefly describe your inquiry or feedback.
   • In the description, provide as much detail as possible to help us understand your request or issue.

We’ll get back to you as soon as possible.

💡 Submit a New Challenge

Want to contribute by submitting a new security challenge to CodeVulnHunt? We’d love to feature it! To ensure consistency and clarity, please fill out the form below:

👉 Submit a New Challenge

📌 Submission Guidelines (One Challenge per Submission)

Please include the following information in your submission:

• Challenge Name: A short, descriptive name.
• Difficulty Level: Choose one — Easy, Medium, or Hard.
• Description: A brief overview of the vulnerable scenario (avoid revealing too much to maintain challenge integrity).
• Solution: Explain how to identify and fix the vulnerability (this will be reviewed and hidden until completion).
• Vulnerability Details:
  • File name (code file name)
  • Category (e.g., SQL Injection, XSS, Insecure Deserialization, etc.).
  • Line Number(s) where each vulnerability exists.
  • Code on line Provide the code snippet from the specified line number
  • If there are multiple vulnerabilities:
    • Specify each line number and its corresponding category.
    • If vulnerabilities span multiple files, include:
      • File name
      • Line number
      • Code on line Provide the code snippet from the specified line number
      • Vulnerability category
• Code Submission:
  • If the challenge consists of multiple files:
    • Create a ZIP of the entire codebase.
    • Upload it to your own Google Drive.
    • Set file access to “Anyone with the link can view.”
    • Paste the Google Drive shareable link in the submission form.

---

📝 Example

• Challenge Name: Broken Auth Bypass in Login Module
• Difficulty Level: Medium
• Description: A login module that lets users bypass authentication under specific conditions.
• Vulnerabilities:
  • File: auth.js
    • Line 42 — Category: Broken Authentication
  • File: config.js
    • Line 15 — Category: Information Exposure
• Solution: Validate user roles on the server side, sanitize input, and avoid exposing sensitive configs in client-side code.
• Code ZIP (Google Drive): drive.google.com/your-shared-link

---

🛑 Please submit one challenge at a time. If you'd like to submit more, just fill out the form separately for each one.

If you have questions or want to report an issue, please open an issue on GitHub.

---

Thanks for contributing and helping others learn secure coding! 💻🔐

🛠️ Looking for Collaborators - CodeVulnHunt Project 🛠️

I'm aware that there are several vulnerabilities on the CodeVulnHunt website. While I'm not a developer, I've done my best to address some of the issues. That said, a few high-severity vulnerabilities still remain. If you're skilled in security or development and are interested in helping out, you're more than welcome to contribute. Please create a request here on GitHub, and if I believe you're capable and have the right skill set, I'll gladly add you to the CodeVulnHunt project. Let's work together to make it better!

🐞 Report an Issue

If you encounter any issues while using the platform, please follow these steps:

1. Open a New Issue in the Issues tab.
2. Provide the following details:
   • Steps to Reproduce: Describe how to replicate the issue.
   • Error Messages: Include any error messages, screenshots, or logs that could help us identify the problem.
   • Browser/Platform Details: Mention the browser and platform (Windows, macOS, Linux, etc.) where the issue occurred.

We’ll investigate the issue and work on fixing it as soon as possible.

⚠️ General Guidelines

• Please use the Issues tab only for contacting us, submitting challenges, or reporting issues. Do not use it for general discussions.
• Be respectful and constructive in your communication.
• Submissions for new challenges should be relevant to improving security awareness and skills.

📜 License and Terms

This repository is not open-source. The CodeVulnHunt platform is privately managed. You are welcome to use this repository for contacting the team, submitting challenges, and reporting issues only.