Magic Fields
magic-fields · plugin
Known security vulnerabilities for Magic Fields. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
3 exploitable without logging in · latest Sep 10, 2019
Closed on wordpress.org
Removed from the directory on Jun 15, 2016 · reason: no reason given. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 7, 2026
Vulnerabilities
- Medium 6.1
CVE-2017-18611unauthenticated · needs a click
The magic-fields plugin before 1.7.2 for WordPress has XSS via the RCCWP_CreateCustomFieldPage.php custom-field-css parameter.
- Medium 6.1
CVE-2017-18610unauthenticated · needs a click
The magic-fields plugin before 1.7.2 for WordPress has XSS via the RCCWP_CreateCustomFieldPage.php custom-group-id parameter.
- Medium 6.1
CVE-2017-18609unauthenticated · needs a click
The magic-fields plugin before 1.7.2 for WordPress has XSS via the custom-write-panel-id parameter.
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).