Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

polylang vulnerabilities and fixes

Recent CVEs affecting polylang, with upgrade or downgrade steps. 1 tracked.

polylang has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2014-07-10. Highest priority: CVE-2014-4855 (score 34/100).

FAQ

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

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

Which polylang CVE should I patch first?

CVE-2014-4855 currently ranks highest (34/100): Cross-site scripting (XSS) vulnerability in the Polylang plugin before 1.5.2 for WordPress allows remote attac.

← Back to latest CVEs