CVE-2026-32359
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in bPlugins Icon List Block icon-list-block allows Stored XSS.This issue affects Icon List Block: from n/a through <= 1.2.3.
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 · moderate confidenceThe bPlugins Icon List Block plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in versions up to 1.2.3. The plugin fails to properly sanitize user-supplied input when creating or editing icon lists, allowing authenticated attackers with contributor-level or higher permissions to inject malicious JavaScript code that executes when other users view the affected content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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 Icon List Block plugin is installedCheck WordPress admin under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'icon-list-block' or similar bPlugins icon list folderAffected if Plugin folder exists in the WordPress plugins directory
-
Determine installed plugin versionView the plugin in WordPress admin plugins list to see the version number, or open the main plugin PHP file and check the 'Version' header in the plugin comment blockAffected if Version displayed is 1.2.3 or lower
-
Identify existing icon list contentQuery WordPress database for posts of type 'wp_block' or custom post type used by the plugin, or check the wp_postmeta table for meta_key values related to icon list settings; alternatively, review any pages/posts where the Icon List Block was usedAffected if Any icon list content exists in the database created by users with contributor-level or higher access
-
Audit user accounts with elevated permissionsNavigate to Users > All Users in WordPress admin and review roles; contributor, author, editor, and administrator roles all have permissions sufficient to exploit this vulnerabilityAffected if Any user accounts with contributor-level or higher permissions exist on the site
Environment is affected if the bPlugins Icon List Block plugin is installed at version 1.2.3 or lower and any icon list content has been created by users with contributor-level or higher permissions.
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.
From vendor dataUpdate the Icon List Block plugin to the latest patched version. Until an update is available, restrict editor-level access to trusted users only and implement additional output escaping where the plugin renders icon content.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32359 — 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-32359 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