SULly

SULly has 4 disclosed vulnerabilities in the WordSec catalog, all reported in 2024; all 4 are fixed as of September 2026. Their average CVSS score is 5.2, and the most serious one scores 6.1 out of 10. 2024 was the busiest year with 4 disclosures.

The most common weakness is Cross-Site Request Forgery (CSRF), behind 2 of the records (50%). Other recurring categories include Cross-Site Scripting.

Every one of the 4 issues recorded for SULly has a vendor fix available, so running the current release closes all known holes.

2 independent researchers contributed these findings, most of them (3) reported by Bob Matyas. SULly is installed on roughly 30 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 6.5.10.

Strategic Overview

Avg CVSSMedium
5.2/ 10
Patch Coverage100%
Open

0

Fixed

4

Get automatic notifications for all SULly vulnerabilities before they are exploited.

Highest severity on recordCVSS 6.1CVE-2024-5032

SULly <= 4.3 - Reflected Cross-Site Scripting

Read the full analysis

Vulnerability Records

4 records
SULly banner
Latestv4.4
5.0(1)
100/100
Last Updated
2024-06-01 (2y ago)
Active Installs
30+
Downloads
3,526
Requires WP
3.7.0+
Requires PHP
0+
Tested up to
WP 6.5.10
Created
2013-11-07 (13y ago)

With WordPress 3.7, updates happen automatically for you, however there is only an e-mail notifications sent. WordPress has a robust administration interface so SULly records all system updates (either automatic or manually done through the admin interface) in to a table and presents the last 10 updates to you in a dashboard widget. Also note that this plugin can only display logs for items installed after SULly itself is installed. This code is released under the GPL v2, see license.txt for details. Roadmap None at this time!

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C