PatchTheCVEmage-people vulnerabilities
Recent CVEs affecting mage-people products. 4 tracked.
mage-people has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2025-06-07. Highest priority: CVE-2024-43138 (score 35/100).
- CVE-2025-5568 MEDIUM 6.4 UPGRADE The WpEvently plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple parameters in all
- CVE-2024-43986 MEDIUM 5.9 UPGRADE Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in M
- CVE-2024-43985 MEDIUM 5.9 UPGRADE Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in M
- CVE-2024-43138 MEDIUM 6.5 UPGRADE Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in MagePeople Tea
FAQ
How do I fix mage-people 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 mage-people being exploited right now?
None of the tracked mage-people CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mage-people CVE should I patch first?
CVE-2024-43138 currently ranks highest (35/100): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in MagePeople Tea.