PatchTheCVEaedating vulnerabilities and fixes
Recent CVEs affecting aedating, with upgrade or downgrade steps. 5 tracked.
aedating has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2006-09-19. Highest priority: CVE-2006-4870 (score 55/100).
- CVE-2006-4870 HIGH 7.5 UPGRADE Multiple PHP remote file inclusion vulnerabilities in AEDating 4.1, and possibly earlier versions, allow remot
- CVE-2006-3279 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in aeDating 4.1 allows remote attackers to inject arbitrary web scrip
- CVE-2005-2985 HIGH 7.5 DOWNGRADE SQL injection vulnerability in search_result.php in AEwebworks aeDating Script 4.0 and earlier allows remote a
- CVE-2005-1084 HIGH 7.5 DOWNGRADE SQL injection vulnerability in sdating.php in aeDating 3.2 allows remote attackers to execute arbitrary SQL co
- CVE-2005-1083 MEDIUM 5.0 DOWNGRADE index.php in aeDating 3.2 allows remote attackers to include arbitrary files via the skin parameter.
FAQ
How do I fix aedating vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is aedating being exploited right now?
None of the tracked aedating CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which aedating CVE should I patch first?
CVE-2006-4870 currently ranks highest (55/100): Multiple PHP remote file inclusion vulnerabilities in AEDating 4.1, and possibly earlier versions, allow remot.