CVE-2026-2382
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FPW Category Thumbnails WordPress plugin suffers from a stored XSS vulnerability in the fpw_fs_get_file AJAX action. Authenticated users with Subscriber-level access can inject malicious scripts via the 'id' parameter due to insufficient input sanitization and output escaping. The payload executes when an administrator accesses the plugin settings page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and versionCheck if FPW Category Thumbnails plugin is installed and note its version number. In WordPress, go to Plugins > Installed Plugins and look for 'FPW Category Thumbnails'. The version is displayed below the plugin name.Affected if The plugin is installed and the version is 1.9.5 or lower (any version up to and including 1.9.5).
-
Confirm AJAX action availabilityInspect the plugin code or check if the fpw_fs_get_file AJAX action is registered and accessible. This typically involves checking the plugin's PHP files for add_action('wp_ajax_fpw_fs_get_file', ...) or similar registration.Affected if The fpw_fs_get_file AJAX action exists in the plugin and is accessible to authenticated users.
-
Check for low-privilege user accountsReview WordPress user roles to determine if there are any users with 'subscriber' role or other low-privilege roles. Go to Users > All Users in the WordPress admin panel and check the roles assigned.Affected if There are one or more user accounts with subscriber-level or lower privileges who can authenticate to the site.
-
Verify plugin settings page accessibilityCheck if the plugin includes a settings or admin page that administrators would access. Look for menu additions in the WordPress admin panel related to the plugin.Affected if The plugin has a settings or configuration page that administrators would view, which would trigger the XSS payload.
The environment is affected if the FPW Category Thumbnails plugin version 1.9.5 or lower is installed, the fpw_fs_get_file AJAX action is accessible, and there are subscriber-level users who could inject malicious code that executes when administrators view the plugin settings page.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to a version beyond 1.9.5 that includes proper input sanitization and output escaping for the 'id' parameter, or implement sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) in the fpw_fs_get_file AJAX handler.
Version 1.9.6 or later (the first fixed release after 1.9.5)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the FPW Category Thumbnails plugin
- 4. If an update is available, click 'Update Now' to install the latest patched version
- 5. Alternatively, download the latest version from wordpress.org/plugins/fpw-category-thumbnails/ and upload manually
- 6. After updating, verify the plugin is active and functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2382 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data