PatchTheCVE2code vulnerabilities
Recent CVEs affecting 2code products. 8 tracked.
2code has 8 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 8. Most recent: 2024-08-05. Highest priority: CVE-2024-2376 (score 45/100).
- CVE-2024-2376 HIGH 8.8 UPGRADE The WPQA Builder WordPress plugin before 6.1.1 does not have CSRF checks in some places, which could allow att
- CVE-2024-2375 MEDIUM 5.4 UPGRADE The WPQA Builder WordPress plugin before 6.1.1 does not sanitise and escape some of its Slider settings, which
- CVE-2024-2235 MEDIUM 4.3 UPGRADE The Himer WordPress theme before 2.1.1 does not have CSRF checks in some places, which could allow attackers t
- CVE-2024-2234 MEDIUM 5.4 UPGRADE The Himer WordPress theme before 2.1.1 does not sanitise and escape some of its Post settings, which could all
- CVE-2024-2233 MEDIUM 4.3 UPGRADE The Himer WordPress theme before 2.1.1 does not have CSRF checks in some places, which could allow attackers t
- CVE-2024-2232 HIGH 8.1 UPGRADE The lacks CSRF checks allowing a user to invite any user to any group (including private groups)
- CVE-2024-2231 MEDIUM 6.5 UPGRADE The allows any authenticated user to join a private group due to a missing authorization check on a function
- CVE-2024-2040 MEDIUM 4.3 UPGRADE The Himer WordPress theme before 2.1.1 does not have CSRF checks in some places, which could allow attackers t
FAQ
How do I fix 2code 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 2code being exploited right now?
None of the tracked 2code CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which 2code CVE should I patch first?
CVE-2024-2376 currently ranks highest (45/100): The WPQA Builder WordPress plugin before 6.1.1 does not have CSRF checks in some places, which could allow att.