CORS-POC is a Proof of Concept web tool designed to detect and exploit Cross-Origin Resource Sharing (CORS) vulnerabilities in websites. With a hacker-style neon interface, this tool allows security researchers and penetration testers to demonstrate the dangers of misconfigured CORS policies by fetching sensitive data from vulnerable domains.
- Simple Input: Enter a vulnerable URL and click "Exploit" to fetch resources.
- Neon Themed UI: Inspired by retro terminal aesthetics for an immersive hacker feel.
- Real-Time Response: Instantly view the fetched resource to verify CORS vulnerability.
- Responsive Design: Fully optimized for desktop and mobile devices.
To use CORS-POC locally, follow these steps:
-
Clone the Repository:
git clone https://github.com/kalmux1/CORS-POC.git
-
Navigate to the Project Directory:
cd CORS-POC
-
Open
index.html
: Launchindex.html
in your preferred web browser to start using CORS-POC locally.
- Enter the Target URL: Paste the URL of the potentially vulnerable website into the input field.
- Click "Exploit": The tool will attempt to fetch resources from the specified URL.
- View Results: The response will be displayed in the textarea, showcasing the success (or failure) of the exploit.
/CORS-POC
├── README.md # Project Documentation
├── LICENSE # LICENSE Documentation
└── docs # Directory for Project Assets
├── CORS ICON.png # Site Icon
└── index.html # Main HTML file for CORS POC
└── script.js # JavaScript Exploit Script
└── style.css # CSS
Contributions are welcome! Follow these steps to contribute to CORS-POC:
- Fork the Repository: Create your own fork of the repository on GitHub.
- Create a New Branch:
git checkout -b feature/your-feature
- Commit Your Changes:
git add . git commit -m "Add your commit message"
- Push to Your Branch:
git push origin feature/your-feature
- Create a Pull Request: Open a pull request on GitHub to propose your changes.
This project is licensed under the MIT License - see the LICENSE file for details.
For any questions or feedback, feel free to reach out via LinkedIn or open an issue on GitHub.