ariadne cms vulnerabilities and fixes
Recent CVEs affecting ariadne cms, with upgrade or downgrade steps. 4 tracked.
Also searched as: ariadnecms.
ariadne cms has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2009-08-31. Highest priority: CVE-2008-7125 (score 52/100).
- CVE-2008-7125 HIGH 9.0 UPGRADE pphoto in Ariadne before 2.6 allows remote authenticated users with certain privileges to execute arbitrary sh
- CVE-2007-2433 MEDIUM 6.8 DOWNGRADE Cross-site scripting (XSS) vulnerability in index.php in Ariadne 2.4.1 allows remote attackers to inject arbit
- CVE-2006-5776 HIGH 7.5 DOWNGRADE Multiple PHP remote file inclusions in Ariadne 2.4.1 allows remote attackers to execute arbitrary PHP code via
- CVE-2005-1181 HIGH 7.5 DOWNGRADE NOTE: this issue has been disputed by the vendor
FAQ
How do I fix ariadne cms 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 ariadne cms being exploited right now?
None of the tracked ariadne cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ariadne cms CVE should I patch first?
CVE-2008-7125 currently ranks highest (52/100): pphoto in Ariadne before 2.6 allows remote authenticated users with certain privileges to execute arbitrary sh.