Read the docs
TI-2024-04674 Aliases CVE-2024-5033GHSA-wh4c-fpvw-r5xc

SULly < 4.3.1 - Admin+ Stored XSS via CSRF

Priority MEDIUM 60CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Required
Attack complexity
Low
Impact type
Tampering
Confidentiality · integrity · availability
Low · Low · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-352.

Summary

The SULly WordPress plugin before 4.3.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00209 11th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA and NVD
Fix Fixed SULly (Unknown): 4.3.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownSULlybefore 4.3.14.3.1Patch availableCNA
  • SULly VendorUnknown Affected before 4.3.1 Fixed in 4.3.1 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:toolstack:sully:*:*:*:*:*:wordpress:*:*before 4.3.1VulnerableToolstack
  • cpe:2.3:a:toolstack:sully:*:*:*:*:*:wordpress:*:* Versions before 4.3.1 Vulnerable ·Toolstack

Remediation

  • Fix · CNA SULly (Unknown) Fixed in 4.3.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    SULly 4.3.1

    4 records Highest priority Priority HIGH 1 HIGH, 3 MEDIUM

    Other records, highest priority first

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-5033
  2. 2026-10-03 Alias added: GHSA-wh4c-fpvw-r5xc

References

Sources