PatchTheCVEaj-fork vulnerabilities
Recent CVEs affecting aj-fork products. 3 tracked.
aj-fork has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2004-12-31. Highest priority: CVE-2004-1571 (score 41/100).
- CVE-2004-1573 HIGH 7.2 DOWNGRADE DOWNGRADE The documentation for AJ-Fork 167 implies that users should set permissions for users.db.php to 777, which all
- CVE-2004-1572 MEDIUM 5.0 DOWNGRADE AJ-Fork 167 does not restrict access to directories such as (1) data, (2) inc, (3) plugins, (4) skins, or (5)
- CVE-2004-1571 MEDIUM 5.0 DOWNGRADE AJ-Fork 167 allows remote attackers to gain sensitive information via a direct request to (1) auto-acronyms.ph
FAQ
How do I fix aj-fork 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 aj-fork being exploited right now?
None of the tracked aj-fork CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which aj-fork CVE should I patch first?
CVE-2004-1571 currently ranks highest (41/100): AJ-Fork 167 allows remote attackers to gain sensitive information via a direct request to (1) auto-acronyms.ph.