What is the CVSS score of EUVD-2026-33887?

EUVD-2026-33887 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

FPW Category Thumbnails EUVD-2026-33887

| CVE-2026-2382 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-06-02 Wordfence

GHSA-c336-945v-ccj3

WordPress XSS Wordpress Plugin Fpw Category Thumbnails

6.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.4 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 02, 2026 - 08:47 vuln.today

CVE Published

Jun 02, 2026 - 07:48 nvd

MEDIUM 6.4

DescriptionCVE.org

The FPW Category Thumbnails plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter of the 'fpw_fs_get_file' AJAX action in all versions up to, and including, 1.9.5. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the plugin's settings page.

AnalysisAI

Stored Cross-Site Scripting in the FPW Category Thumbnails WordPress plugin (all versions ≤1.9.5) allows authenticated attackers with Subscriber-level access to plant persistent JavaScript payloads via the unsanitized 'id' parameter of the 'fpw_fs_get_file' AJAX action. The injected script executes in an administrator's browser upon visiting the plugin's settings page, creating a privilege-escalation pathway from low-privileged subscriber to effective site administrator. No public exploit has been identified and the vulnerability is not listed in CISA KEV at time of analysis, but the low attack complexity and Changed Scope signal meaningful risk in open-registration WordPress environments.

Technical ContextAI

The FPW Category Thumbnails plugin (vendor: frankpw; CPE: cpe:2.3:a:frankpw:fpw_category_thumbnails:*:*:*:*:*:*:*:*) provides category thumbnail management functionality for WordPress. The vulnerability is rooted in CWE-79 (Improper Neutralization of Input During Web Page Generation): user-supplied data passed via the 'id' parameter to the AJAX action 'fpw_fs_get_file' is neither sanitized on input nor escaped on output before being written into HTML rendered in the browser. Source code confirmed by Wordfence spans three files in version 1.9.5: the primary injection point at ajax/getimageid.php (line 10), a rendering sink at code/table.php (line 53), and the plugin class handler at classes/fpw-category-thumbnails-class.php (line 54). Because the payload is stored server-side and later rendered to an administrator, this is a persistent (Stored) XSS rather than a reflected one, increasing its impact relative to other XSS classes.

RemediationAI

No patched version has been identified in the available data - the Wordfence advisory and SVN repository references confirm vulnerable code only through version 1.9.5, and no fixed release version has been independently confirmed. Administrators should monitor the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/1fdbddd7-8713-48c8-98d6-0a155ca68325 and the WordPress plugin repository for an updated release. As an immediate compensating control, deactivate or uninstall the FPW Category Thumbnails plugin entirely until a patched version is available; this eliminates the attack surface with no meaningful side effect beyond losing the thumbnail categorization feature. If the plugin cannot be removed due to operational requirements, disable open WordPress user registration to prevent untrusted subscribers from being created - note this impacts any user self-service flows. A WAF rule blocking POST requests containing the 'fpw_fs_get_file' action parameter can suppress exploitation attempts but should not be treated as a permanent fix, as bypass techniques may exist.