Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

tagregator vulnerabilities and fixes

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

tagregator has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-05-05. Highest priority: CVE-2018-10752 (score 41/100).

FAQ

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

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

Which tagregator CVE should I patch first?

CVE-2018-10752 currently ranks highest (41/100): The Tagregator plugin 0.6 for WordPress has stored XSS via the title field in an Add New action..

← Back to latest CVEs