PatchTheCVEfreakingwildchild vulnerabilities
Recent CVEs affecting freakingwildchild products. 1 tracked.
freakingwildchild has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2024-09-17. Highest priority: CVE-2024-8047 (score 31/100).
- CVE-2024-8047 MEDIUM 6.5 UPGRADE The Visual Sound (old) WordPress plugin through 1.06 does not have CSRF check in place when updating its setti
FAQ
How do I fix freakingwildchild 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 freakingwildchild being exploited right now?
None of the tracked freakingwildchild CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which freakingwildchild CVE should I patch first?
CVE-2024-8047 currently ranks highest (31/100): The Visual Sound (old) WordPress plugin through 1.06 does not have CSRF check in place when updating its setti.