SULly
sully · plugin
Known security vulnerabilities for SULly. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
latest Jul 13, 2024
Before you install
Use with care
- Last updated Jun 1, 2024: not updated for more than two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
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 4.4 · last updated Jun 1, 2024 · 30+ installs
Not updated since Jun 1, 2024. A component left without updates for over two years should not be expected to patch new vulnerabilities.
wordpress.org status checked on Nov 1, 2026
Vulnerabilities
- High 8.8
CVE-2024-5034login required→ 4.3.1
SULly < 4.3.1 - Plugin Reset via CSRF
- High 7.1
CVE-2024-5151admin→ 4.3.1
SULly < 4.3.1 - Admin+ Stored XSS
- Medium 5.9
CVE-2024-5033admin→ 4.3.1
SULly < 4.3.1 - Admin+ Stored XSS via CSRF
- Medium 4.7
CVE-2024-5032admin→ 4.3.1
SULly < 4.3.1 - Reflected XSS
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).