sweet-cms vulnerabilities and fixes

Recent CVEs affecting sweet-cms, with upgrade or downgrade steps. 2 tracked.

Also searched as: sweet cms.

sweet-cms has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2024-08-30. Highest priority: CVE-2024-8332 (score 39/100).

• CVE-2024-8334 MEDIUM 4.3 UPGRADE A vulnerability was found in master-nan Sweet-CMS up to 5f441e022b8876f07cde709c77b5be6d2f262e3f
• CVE-2024-8332 MEDIUM 6.3 UPGRADE A vulnerability was found in master-nan Sweet-CMS up to 5f441e022b8876f07cde709c77b5be6d2f262e3f

FAQ

How do I fix sweet-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 sweet-cms being exploited right now?

None of the tracked sweet-cms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which sweet-cms CVE should I patch first?

CVE-2024-8332 currently ranks highest (39/100): A vulnerability was found in master-nan Sweet-CMS up to 5f441e022b8876f07cde709c77b5be6d2f262e3f.

← Back to latest CVEs