fullworksplugins CVE Vulnerabilities & Metrics

Focus on fullworksplugins vulnerabilities and metrics.

Last updated: 15 Feb 2026, 23:25 UTC

About fullworksplugins Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with fullworksplugins. 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 fullworksplugins CVEs: 13
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 fullworksplugins CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 0.72

Max CVSS: 5.0

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 11
4.0-6.9 2
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS fullworksplugins CVEs

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

All CVEs for fullworksplugins

CVE-2025-4302 fullworksplugins 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-2023-1554 fullworksplugins vulnerability CVSS: 0 02 May 2023, 08:15 UTC

The Quick Paypal Payments WordPress plugin before 5.7.26.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Paypal Payments plugin <= 5.7.25 versions.

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Contact Form plugin <= 8.0.3.1 versions.

Unauth. Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Paypal Payments plugin <= 5.7.25 versions.

Auth. (admin+) Stored Cross-site Scripting (XSS) vulnerability in Fullworks Quick Paypal Payments plugin <= 5.7.25 versions.

Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Contact Form plugin <= 8.0.3.1 versions.

Unauth. Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Event Manager plugin <= 9.7.4 versions.

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Fullworks Quick Event Manager plugin <= 9.6.4 versions.

Cross-Site Request Forgery (CSRF) vulnerability in Fullworks Quick Event Manager plugin <= 9.7.4 affecting all registration actions (delete, delete all, edit, update).

The Quick Event Manager WordPress Plugin, version < 9.7.5, is affected by a reflected cross-site scripting vulnerability in the 'category' parameter of its 'qem_ajax_calendar' action.

CVE-2017-18536 fullworksplugins 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 fullworksplugins vulnerability CVSS: 5.0 17 Nov 2017, 05:29 UTC

Stop User Enumeration 1.3.8 allows user enumeration via the REST API