PatchTheCVEprojectforge vulnerabilities and fixes
Recent CVEs affecting projectforge, with upgrade or downgrade steps. 3 tracked.
projectforge has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2014-01-02. Highest priority: CVE-2013-7251 (score 45/100).
- CVE-2013-7251 MEDIUM 6.8 UPGRADE Multiple cross-site request forgery (CSRF) vulnerabilities in ProjectForge before 5.3 allow remote attackers t
- CVE-2013-7250 LOW 3.5 UPGRADE Cross-site scripting (XSS) vulnerability in the JsonBuilder implementation in ProjectForge before 5.3 allows r
- CVE-2011-5269 LOW 3.5 UPGRADE Cross-site scripting (XSS) vulnerability in ProjectForge before 3.5.3 allows remote authenticated users to inj
FAQ
How do I fix projectforge 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 projectforge being exploited right now?
None of the tracked projectforge CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which projectforge CVE should I patch first?
CVE-2013-7251 currently ranks highest (45/100): Multiple cross-site request forgery (CSRF) vulnerabilities in ProjectForge before 5.3 allow remote attackers t.