PatchTheCVEpublify project vulnerabilities
Recent CVEs affecting publify project products. 4 tracked.
publify project has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2023-01-29. Highest priority: CVE-2022-1812 (score 69/100).
- CVE-2023-0569 MEDIUM 6.5 UPGRADE Weak Password Requirements in GitHub repository publify/publify prior to 9.2.10.
- CVE-2023-0299 CRITICAL 9.8 UPGRADE Improper Input Validation in GitHub repository publify/publify prior to 9.2.10.
- CVE-2022-2815 MEDIUM 6.5 UPGRADE Insecure Storage of Sensitive Information in GitHub repository publify/publify prior to 9.2.10.
- CVE-2022-1812 CRITICAL 9.8 UPGRADE Integer Overflow or Wraparound in GitHub repository publify/publify prior to 9.2.10.
FAQ
How do I fix publify project 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 publify project being exploited right now?
None of the tracked publify project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which publify project CVE should I patch first?
CVE-2022-1812 currently ranks highest (69/100): Integer Overflow or Wraparound in GitHub repository publify/publify prior to 9.2.10..