DOCSEARCHbyAlgolia
Submit Docs

GDorks

repository·main·Indexed 20 days ago

https://github.com/ishanoshada/gdorks

A repository of Google Dorks (advanced search queries) used to uncover hidden information, sensitive files, and security vulnerabilities. It includes specialized dorks for CCTV, Joomla, Laravel, and Local File Inclusion (LFI), as well as a large collection of 1M dorks segmented into 50 files. The repository covers various vulnerability categories including SQL Injection, XSS, Path Traversal, RFI, XXE, and Command Injection. Users can access the data by cloning the repository or via the GDorks Web App.

Tokens
7.6K
Snippets
21
Records
43
Agent score
71%

What's inside GDorks

  1. Ethical guidelines for CCTV security research

    main

    When exploring CCTV vulnerabilities or conducting security research, you must adhere to the following ethical guidelines:

    • Responsible Disclosure: If you identify a vulnerability, report it directly to the appropriate authorities or the system owners.
    • Legal Compliance: Respect all privacy laws and ensure you do not engage in any activity that violates local or international regulations.
    • Avoid Intrusive Actions: Never attempt unauthorized access to CCTV systems or exploit vulnerabilities without explicit, documented permission from the system owner.

  2. Common Laravel security vulnerabilities

    main

    When auditing Laravel applications, be aware of these common vulnerability classes:

    • SQL Injection: Occurs if user inputs are not properly sanitized before being used in database queries.
    • Sensitive Data Exposure: Occurs when files like .env, config/, or storage/ are publicly accessible.
    • Cross-Site Scripting (XSS): Occurs due to insecure handling of user input in the browser.

  3. Identify common WordPress vulnerabilities

    main

    When auditing WordPress sites, be aware of these common vulnerability classes:

    • SQL Injection: Often found in poorly coded plugins or themes.
    • Cross-Site Scripting (XSS): Can exist in various parts of the site, leading to client-side attacks.
    • File Inclusion: Caused by improper file handling.
    • Directory Traversal: Allows unauthorized access to files and directories.

  4. What are Google Dorks?

    main
    Google dorks are specially crafted search queries that use advanced search operators to fine-tune Google searches. They allow users to focus on specific results and uncover information that standard searches might miss.

  5. Understand Google Dorks and Ethical Usage

    main

    What are Google Dorks?

    Google dorks are specialized search queries that use advanced search operators to refine Google searches. They help users find specific information that might be overlooked in regular searches.

    Ethical Guidelines and Disclaimer

    GDorks is intended for educational purposes only.

    • Do not use these for malicious activities.
    • Respect privacy and intellectual property.
    • Abide by all laws and regulations.
    • Report security vulnerabilities responsibly to the website owner or administrator rather than exploiting them.

  7. Contribute Joomla dorks to the repository

    main

    To add new Joomla dorks, examples, or documentation to this repository, follow these steps:

    1. Fork the repository.
    2. Create a new branch with a descriptive name.
    3. Add your Joomla dorks or other content.
    4. Submit a pull request.

  9. Explore Git, Configuration, and WordPress Dorks

    main

    GDorks provides specialized search queries to find specific types of files and directories. Use these queries to identify exposed repositories, configuration settings, or CMS-specific files.

    Git Repositories filetype:git web inurl:git

    Configuration Files

    • General: filetype:conf inurl:web.config
    • Environment files with AWS keys: filetype:env intext:AWS_SECRET_ACCESS_KEY
    • WordPress config: filetype:txt inurl:wp-config

    WordPress & PHP

    • WordPress Admin: inurl:/wp-admin
    • PHP Info files: filetype:php inurl:info
    • WordPress Themes: inurl:/wp-content/themes/ intitle:"Index of"

    Other Categories

    • Open Directories: intitle:"Index of /" + "backup"
    • Google Drive Links: inurl:"/uc?id="
    • AWS Private Keys: filetype:pem intext:PRIVATE KEY
    filetype:git inurl:git
filetype:conf inurl:web.config
filetype:php inurl:info
inurl:/wp-admin
intitle:"Index of /" + "backup"
inurl:"/uc?id="
filetype:txt inurl:wp-config
filetype:pem intext:PRIVATE KEY
filetype:env intext:AWS_SECRET_ACCESS_KEY

  10. How to use the More Dorks repository

    main
    The repository is organized into folders based on vulnerability categories. To perform security testing, navigate to the specific folder corresponding to the vulnerability type you are investigating (e.g., SQL Injection, XSS, Path Traversal). Each category folder contains a README file providing detailed information and specific dork examples relevant to that category.

  11. Use WordPress Dorks to identify security weaknesses

    main

    WordPress dorks are specialized search queries used to identify potential security weaknesses or loopholes in websites powered by the WordPress CMS. Common use cases include identifying versions, login pages, configuration files, and plugin directories.

    1. WordPress Version Check: inurl:/readme.html
2. WordPress Login Page: inurl:/wp-login.php
3. WordPress Configuration File: inurl:wp-config.php
4. WordPress Database Information: inurl:/wp-admin/setup-config.php
5. WordPress Plugins: inurl:/wp-content/plugins/

  12. How to use the SQLi Dorks repository

    main
    The repository is organized into folders, each containing specific SQL Injection (SQLi) dorks and related information. To use the resource, browse through the folders to find dorks categorized by the specific type of SQLi vulnerability or attack vector you are researching.