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

CVE-2026-57387

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 picu picu picu allows Stored XSS.This issue affects picu: from n/a through <= 3.5.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 · high confidence

The picu WordPress plugin versions up to 3.5.1 contains a stored cross-site scripting (XSS) vulnerability due to improper neutralization of user-supplied input during web page generation. Malicious scripts can be injected through plugin input fields and persistently stored, executing in the browsers of all users who view the affected content.

MitigationUpdate picu to the latest version when available, or implement proper input validation and output encoding on all user-submitted data before rendering in HTML contexts.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify picu plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'picu' in the list, or check the /wp-content/plugins/ directory for a picu folder
    Affected if picu plugin is present in the WordPress installation
  2. Determine installed picu version
    In WordPress admin, go to Plugins > Installed Plugins, find picu, and note the version number displayed below the plugin name; alternatively, check the picu plugin main file (e.g., picu.php) for the 'Version' header comment
    Affected if the version is 3.5.1 or lower (any version up to and including 3.5.1)
  3. Identify plugin input fields that accept user data
    In the WordPress admin, navigate to picu plugin settings, collection creation forms, or client-facing submission pages where users enter data (e.g., client names, email addresses, collection titles)
    Affected if the plugin accepts and stores user-supplied input through web forms
  4. Inspect stored data for suspicious scripts
    Check the WordPress database tables where picu stores user input (typically wp_posts, wp_postmeta, or custom picu tables) for HTML script tags, javascript: URIs, or event handler attributes in stored values
    Affected if any stored data contains unencoded HTML or script tags that could execute in a browser

A user is affected if the picu plugin is installed with version 3.5.1 or lower AND the plugin processes user-supplied input that gets rendered without proper encoding.

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 picu to the latest version when available, or implement proper input validation and output encoding on all user-submitted data before rendering in HTML contexts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57387 — 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-57387 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