PatchTheCVEs-notify vulnerabilities and fixes
Recent CVEs affecting s-notify, with upgrade or downgrade steps. 6 tracked.
Also searched as: s notify.
s-notify has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2024-07-01. Highest priority: CVE-2023-50932 (score 31/100).
- CVE-2024-23737 MEDIUM 5.4 UPGRADE UPGRADE Cross Site Request Forgery (CSRF) vulnerability in savignano S/Notify before 4.0.2 for Jira allows attackers t
- CVE-2024-23735 MEDIUM 6.1 UPGRADE Cross Site Scripting (XSS) vulnerability in in the S/MIME certificate upload functionality of the User Profile
- CVE-2024-23734 MEDIUM 5.2 UPGRADE Cross Site Request Forgery vulnerability in in the upload functionality of the User Profile pages in savignano
- CVE-2023-50932 HIGH 8.3 UPGRADE An issue was discovered in savignano S/Notify before 4.0.2 for Confluence
- CVE-2023-50931 HIGH 8.3 UPGRADE An issue was discovered in savignano S/Notify before 2.0.1 for Bitbucket
- CVE-2023-50930 HIGH 8.3 UPGRADE An issue was discovered in savignano S/Notify before 4.0.2 for Jira
FAQ
How do I fix s-notify 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 s-notify being exploited right now?
None of the tracked s-notify CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which s-notify CVE should I patch first?
CVE-2023-50932 currently ranks highest (31/100): An issue was discovered in savignano S/Notify before 4.0.2 for Confluence.