WP Stacker
wp-stacker · plugin
Known security vulnerabilities for WP Stacker. Find out in seconds which version runs on your site with WP Lens.
1 known vulnerabilities
1 exploitable without logging in · 1 with no official fix seen · latest Jun 7, 2024
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- Last updated Feb 23, 2016: not updated for more than 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
Listed on wordpress.org · latest 1.8.5 · last updated Feb 23, 2016 · 10+ installs
Not updated since Feb 23, 2016. A component left without updates for over two years should not be expected to patch new vulnerabilities.
wordpress.org status checked on Oct 19, 2026
Vulnerabilities
- Medium 5.4
CVE-2024-5003unauthenticated · needs a clickno fix seen
WP Stacker <= 1.8.5 - Stored XSS via CSRF
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). The record lists the latest wordpress.org release (1.8.5) as affected.