dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-32419

MEDIUM · 5.9 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Fernando Briano List category posts list-category-posts allows DOM-Based XSS.This issue affects List category posts: from n/a through <= 0.93.1.

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 confidence

DOM-based Cross-site Scripting (XSS) vulnerability in the List Category Posts WordPress plugin allows unauthenticated attackers to inject malicious JavaScript through unsanitized user input that gets reflected in the page DOM.

MitigationUpdate the plugin to a version beyond 0.93.1 that includes proper input sanitization for DOM-based XSS prevention; alternatively, implement output encoding on user-controlled inputs before rendering them in the browser.

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
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the List Category Posts plugin directory
    Check the wp-content/plugins/ directory on the WordPress server for a folder named 'list-category-posts' or similar variation
    Affected if The plugin directory exists on the server
  2. Find the installed version number
    Open the main plugin PHP file (usually list-category-posts.php) and read the Version field from the plugin header comment at the top of the file
    Affected if The version is 0.93.1 or lower, or if the version cannot be determined but the plugin is present
  3. Verify the plugin is active
    Query the WordPress database wp_options table for the option 'active_plugins', or use the WordPress admin interface to check if List Category Posts appears in the list of active plugins
    Affected if The plugin appears in the active plugins list and is enabled on the site
  4. Identify user input reflection points
    Review the plugin source code for parameters that accept user input (like catlist, id, template, or custom shortcode attributes) and are output directly to the page HTML/DOM without sanitization functions such as esc_html(), esc_attr(), or wp_kses()
    Affected if Code analysis reveals unsanitized echo statements that reflect shortcode attributes or query parameters directly into the page output

The site is affected if the List Category Posts plugin is installed, active, and running version 0.93.1 or lower where user-supplied input is reflected into the DOM without proper escaping.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 0.93.1 that includes proper input sanitization for DOM-based XSS prevention; alternatively, implement output encoding on user-controlled inputs before rendering them in the browser.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32419 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32419 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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