fullworks CVE Vulnerabilities & Metrics

Focus on fullworks vulnerabilities and metrics.

Last updated: 16 Jan 2026, 23:25 UTC

About fullworks Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with fullworks. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total fullworks CVEs: 4
Earliest CVE date: 17 Nov 2017, 05:29 UTC
Latest CVE date: 17 Jul 2025, 08:15 UTC

Latest CVE reference: CVE-2025-4302

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): 0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical fullworks CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 3.4

Max CVSS: 5.0

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range	Count
0.0-3.9	1
4.0-6.9	3
7.0-8.9	0
9.0-10.0	0

CVSS Distribution Chart

Top 5 Highest CVSS fullworks CVEs

These are the five CVEs with the highest CVSS scores for fullworks, sorted by severity first and recency.

CVE-2017-1000226 fullworks Published on 17 Nov 2017, 05:29 UTC (CVSS: 5.0)
Stop User Enumeration 1.3.8 allows user enumeration via the REST API
CVE-2021-24767 fullworks Published on 08 Nov 2021, 18:15 UTC (CVSS: 4.3)
The Redirect 404 Error Page to Homepage or Custom Page with Logs WordPress plugin before 1.7.9 does not check for CSRF when deleting logs, which could allow attacker to make a logged in admin delete them via a CSRF attack
CVE-2017-18536 fullworks Published on 21 Aug 2019, 12:15 UTC (CVSS: 4.3)
The stop-user-enumeration plugin before 1.3.8 for WordPress has XSS.
CVE-2025-4302 fullworks Published on 17 Jul 2025, 08:15 UTC (CVSS: 0)
The Stop User Enumeration WordPress plugin before version 1.7.3 blocks REST API /wp-json/wp/v2/users/ requests for non-authorized users. However, this can be bypassed by URL-encoding the API path.

All CVEs for fullworks

CVE-2025-4302 fullworks vulnerability CVSS: 0 17 Jul 2025, 08:15 UTC

The Stop User Enumeration WordPress plugin before version 1.7.3 blocks REST API /wp-json/wp/v2/users/ requests for non-authorized users. However, this can be bypassed by URL-encoding the API path.

CVE-2021-24767 fullworks vulnerability CVSS: 4.3 08 Nov 2021, 18:15 UTC

The Redirect 404 Error Page to Homepage or Custom Page with Logs WordPress plugin before 1.7.9 does not check for CSRF when deleting logs, which could allow attacker to make a logged in admin delete them via a CSRF attack

CVE-2017-18536 fullworks vulnerability CVSS: 4.3 21 Aug 2019, 12:15 UTC

The stop-user-enumeration plugin before 1.3.8 for WordPress has XSS.

CVE-2017-1000226 fullworks vulnerability CVSS: 5.0 17 Nov 2017, 05:29 UTC

Stop User Enumeration 1.3.8 allows user enumeration via the REST API