magic fields vulnerabilities and fixes

Recent CVEs affecting magic fields, with upgrade or downgrade steps. 3 tracked.

Also searched as: magicfields.

magic fields has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2019-09-10. Highest priority: CVE-2017-18611 (score 43/100).

• CVE-2017-18611 MEDIUM 6.1 UPGRADE The magic-fields plugin before 1.7.2 for WordPress has XSS via the RCCWP_CreateCustomFieldPage.php custom-fiel
• CVE-2017-18610 MEDIUM 6.1 UPGRADE The magic-fields plugin before 1.7.2 for WordPress has XSS via the RCCWP_CreateCustomFieldPage.php custom-grou
• CVE-2017-18609 MEDIUM 6.1 UPGRADE The magic-fields plugin before 1.7.2 for WordPress has XSS via the custom-write-panel-id parameter.

FAQ

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

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

Which magic fields CVE should I patch first?

CVE-2017-18611 currently ranks highest (43/100): The magic-fields plugin before 1.7.2 for WordPress has XSS via the RCCWP_CreateCustomFieldPage.php custom-fiel.

RSS feed for magic fields · ← Back to latest CVEs