# CVEFinder.io > Real-time CVE vulnerability scanner and intelligence platform ## Overview CVEFinder.io is a security intelligence platform that scans websites to identify technologies and their associated CVE vulnerabilities. The platform combines automated technology detection with a comprehensive CVE database to help organizations understand their attack surface. **Website:** https://cvefinder.io ## Core Features - **Website Vulnerability Scanning** - Detect technologies and associated CVEs on any public website - **Bulk Scan Mode** - Scan up to 20 URLs simultaneously (Pro feature) - **CVE Database** - Searchable database of CVEs with severity ratings, CVSS/EPSS scores, and exploit information - **Technology Detection** - Identify web technologies, versions, and frameworks via header/HTML/JavaScript analysis - **Vendor & Product Intelligence** - Browse CVEs by vendor/product relationships - **Monitoring & Alerts** - Track URLs for new vulnerabilities (Pro feature) - **Exploit Database** - Access PoC code and exploit information (Pro feature) ## URL Structure ### Main Pages - `/` - Homepage with scan interface - `/search?q={query}` - Search CVEs, products, and vendors - `/pricing` - Pricing plans and features - `/login` - Passwordless OTP authentication - `/account` - User dashboard (requires login) ### Data Pages - `/cve/{cve_id}` - CVE detail pages (e.g., `/cve/CVE-2024-1234`) - `/product/{id}` - Product pages with all associated CVEs - `/vendor/{id}` - Vendor pages with products and CVE statistics - `/scan/{id}` - Scan result pages with detected technologies and CVEs - `/bulk-scan/{id}` - Bulk scan result pages with progress tracking (Pro only) ### Legal - `/privacy-policy` - Privacy policy - `/terms-and-conditions` - Terms of service ## API Endpoints ### Public APIs ``` GET /api/search?q={query} - Search CVEs, products, vendors GET /api/recent-cves?limit=10 - Latest CVEs added to database GET /api/recent-scans - Latest public scans POST /api/scan - Submit website for scanning ``` ### Authenticated APIs (requires JWT token) ``` GET /api/product-cves?product_id={id} - CVEs for specific product GET /api/vendor-products?vendor_id={id} - Products for specific vendor POST /api/bulk-scan - Submit multiple URLs for scanning (Pro only) GET /api/get-bulk-scan?id={id} - Get bulk scan status and progress (Pro only) GET /api/account-recent-bulk-scans - Get user's recent bulk scans (Pro only) ``` **Authentication:** Bearer token in Authorization header ``` Authorization: Bearer {jwt_token} ``` ## Pricing Plans | Feature | Guest | Free | Pro | |---------|-------|------|-----| | **Price** | $0 | $0 | $9/month | | **Daily Scans** | 1 | 3 | 20 | | **Bulk Scan Mode** | ❌ | ❌ | ✅ (20 URLs) | | **CVE Database Access** | ❌ | ✅ | ✅ | | **Technology Detection** | ✅ | ✅ | ✅ | | **Version Detection** | ✅ | ✅ | ✅ | | **Private Scans** | ❌ | ✅ | ✅ | | **Exploit Database** | ❌ | ❌ | ✅ | | **API Keys** | ❌ | ❌ | ✅ | | **JSON Exports** | ❌ | ❌ | ✅ | | **Version-based CVE Filtering** | ❌ | ❌ | ✅ | | **Manual Rescan/Refresh** | ❌ | ❌ | ✅ | | **Email Monitoring** | ❌ | ❌ | ✅ (5 URLs) | | **Product/Vendor Alerts** | ❌ | ❌ | ✅ (10 max) | ## Data Structure ### CVE Records Each CVE includes: - CVE ID (e.g., CVE-2024-1234) - Summary and detailed description - Severity level (LOW, MEDIUM, HIGH, CRITICAL) - CVSS Score (v3.1 and v4.0) - EPSS Score (Exploit Prediction Scoring System) - CWE IDs (Common Weakness Enumeration) - Published and last modified dates - References and source URLs - Affected products with version ranges ### Products - Product name and vendor - Version information - Associated CVEs with affected/unaffected version ranges - CVE count by severity ### Vendors - Vendor/organization name - All products under vendor - Total CVE statistics - Severity breakdown ### Scan Results - Domain and URL scanned - Detected technologies with versions - Detection method (header, HTML, JavaScript, cookies) - Confidence scores (0-100%) - Associated CVEs for each technology - Scan timestamp - Public/private status ### Exploits (Pro Only) - Exploit source (ExploitDB, GitHub, Metasploit, PacketStorm) - Exploit type (remote, local, webapps, DoS, PoC) - Platform and verification status - PoC code snippets ## Technology Detection CVEFinder detects technologies through: 1. **HTTP Headers** - Server headers, X-Powered-By, etc. 2. **HTML Content** - Meta tags, generator tags, comments 3. **JavaScript** - Global objects, library detection 4. **Cookies** - Session cookie patterns Each detection includes: - Technology name (e.g., "WordPress", "Nginx", "PHP") - Version (if detected) - Detection method - Confidence score (0-100%) ## Use Cases ### For Security Professionals - Perform reconnaissance during penetration testing - Identify outdated technologies with known vulnerabilities - Assess third-party vendor security posture - Monitor critical assets for new CVEs ### For Developers - Check dependencies for known vulnerabilities - Research CVEs affecting specific technologies - Monitor production sites for security issues - Export scan data for CI/CD integration ### For Researchers - Search and explore CVE database - Track vulnerability trends by vendor/product - Analyze exploit availability and EPSS scores - Research vulnerability disclosure timelines ## Rate Limits - **Guest Users:** 1 scan per day - **Free Users:** 3 scans per day - **Pro Users:** 20 scans per day (including bulk scan mode for up to 20 URLs at once) **Note:** Previously scanned URLs don't count toward your daily limit ## Authentication CVEFinder uses **passwordless authentication** via OTP (One-Time Password): 1. User enters email address 2. System sends 6-digit OTP code via email 3. User enters OTP code 4. System returns JWT token for authenticated requests ## Data Freshness - **CVE Database:** Synced daily from NVD (National Vulnerability Database) - **EPSS Scores:** Updated daily from FIRST.org - **Exploit Database:** Updated regularly from multiple sources - **Scan Results:** Real-time detection, no caching ## Sitemap - Main sitemap: `/sitemap.xml` - CVE pages: `/sitemaps/sitemap-cves-*.xml` - Vendor pages: `/sitemaps/sitemap-vendors-*.xml` - Product pages: `/sitemaps/sitemap-products-*.xml` ## SEO & Indexing - Public scans: Indexed by search engines - Private scans: `noindex, nofollow` meta tag - CVE/product/vendor pages: Fully indexed - Schema.org markup: FAQPage, BreadcrumbList, WebApplication - Open Graph tags for social sharing ## Privacy & Security - Anonymous scanning available (public results) - Authenticated users get private scan storage - No passwords stored (OTP-based authentication) - JWT tokens for stateless authentication - Rate limiting to prevent abuse - No data collection beyond functional requirements ## Technical Stack - **Backend:** PHP with MySQL/InnoDB - **Frontend:** Bootstrap 5, vanilla JavaScript - **Authentication:** JWT with OTP email delivery - **Payment:** Razorpay (India) - credit cards, UPI, wallets - **Detection Engine:** Custom regex-based technology detection ## Contact & Support - **Website:** https://cvefinder.io - **Pricing:** https://cvefinder.io/pricing - **Search:** https://cvefinder.io/search - **Login:** https://cvefinder.io/login ## Example Usage ### Scan a website 1. Visit https://cvefinder.io 2. Enter domain or URL (e.g., "example.com") 3. View detected technologies 4. Sign up (free) to see associated CVEs ### Search CVE database 1. Visit https://cvefinder.io/search 2. Enter CVE ID, product name, or keyword 3. Browse results with severity filtering 4. Click any result for detailed CVE information ### Monitor a URL (Pro) 1. Log in to Pro account 2. Scan target URL 3. Enable monitoring from scan results 4. Receive email alerts when new CVEs are published ## Notes for LLMs - CVEFinder.io focuses on **detection, not exploitation** - Technology detection is confidence-based (scores 0-100%) - CVE data sourced from official NVD database - Exploit information available only to Pro users - All scans are performed against public websites only - Private scans are only visible to the scan owner - Guest scans are public and visible on homepage - EPSS scores help prioritize vulnerability remediation - Version detection accuracy depends on server headers and HTML content