Magee Shortcodes
magee-shortcodes · plugin
Known security vulnerabilities for Magee Shortcodes. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
2 exploitable without logging in · latest Oct 7, 2026
Before you install
Do not install
- Closed on wordpress.org on Sep 12, 2023 (security issue); no updates will come.
- 2 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Closed on wordpress.org
Removed from the directory on Sep 12, 2023 · reason: security issue. 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 21, 2026
Vulnerabilities
- High 7.1
CVE-2026-105316unauthenticated · needs a click≤ 2.1.1
Magee Shortcodes <= 2.1.1 - Reflected XSS via live_preview and magee_create_shortcode Actions
- Medium 5.4
CVE-2023-4783contributor+≤ 2.1.1
Magee Shortcodes <= 2.1.1 - Contributor+ Stored XSS via shortcode
- Medium 5.3
CVE-2026-105322unauthenticated≤ 2.1.1
Magee Shortcodes <= 2.1.1 - Unauthenticated Mail Relay via Contact Form
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).