PatchTheCVEmantus667 vulnerabilities
Recent CVEs affecting mantus667 products. 3 tracked.
mantus667 has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2025-05-15. Highest priority: CVE-2024-13875 (score 35/100).
- CVE-2025-2248 MEDIUM 5.4 UPGRADE The WP-PManager WordPress plugin through 1.2 does not sanitize and escape a parameter before using it in a SQL
- CVE-2025-2247 MEDIUM 5.4 UPGRADE The WP-PManager WordPress plugin through 1.2 does not have CSRF check in place when updating its settings, whi
- CVE-2024-13875 HIGH 7.1 UPGRADE The WP-PManager WordPress plugin through 1.2 does not sanitise and escape a parameter before outputting it bac
FAQ
How do I fix mantus667 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 mantus667 being exploited right now?
None of the tracked mantus667 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mantus667 CVE should I patch first?
CVE-2024-13875 currently ranks highest (35/100): The WP-PManager WordPress plugin through 1.2 does not sanitise and escape a parameter before outputting it bac.