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

CVE-2026-5742

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

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
The UsersWP plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.2.60. This is due to insufficient input sanitization of user-supplied URL fields and improper output escaping when rendering user profile data in badge widgets. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts that will execute whenever a user accesses a page containing the affected badge widget.

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 UsersWP WordPress plugin fails to properly sanitize user-supplied URL fields and escape output when rendering badge widgets, allowing stored XSS injection. Authenticated attackers with subscriber-level access can embed malicious scripts into profile URL fields that execute when other users view pages containing the affected badge widget.

MitigationUpdate UsersWP to the latest version which includes proper input sanitization and output escaping for URL fields in badge widgets. If no update is available, implement sanitization (esc_url()) and output escaping (esc_html()/esc_attr()) on all user profile URL fields before rendering.

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 checks

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

  1. Verify UsersWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for UsersWP, or check the plugins directory for the userswp folder. Note the installed version number.
    Affected if UsersWP plugin is installed and active
  2. Compare installed version to affected range
    Check the version number noted in step 1 against the affected version range for this CVE (vulnerable versions prior to the patched release). Consult the WordPress plugin repository or your plugin changelog for the specific version that addresses this issue.
    Affected if Installed version falls within the vulnerable version range and has not been patched
  3. Identify active badge widgets
    Check your WordPress widgets dashboard (Appearance > Widgets) and page builders for any instantiated UsersWP badge widgets. Also search for shortcodes like [uwp_badge] in your pages and posts.
    Affected if Badge widgets are actively displayed on any public-facing pages
  4. Inspect user profile URL fields
    Query the usermeta table for users with non-empty 'url' or 'website' meta values that may contain script tags. Example SQL: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'url' AND meta_value LIKE '%<script%'
    Affected if Any user profile URL fields contain unescaped HTML or script tags
  5. Verify output escaping in badge widget code
    Examine the UsersWP plugin files, specifically the badge widget rendering code (typically in includes/widgets or templates folders). Look for esc_url(), esc_html(), or esc_attr() functions wrapping user-supplied URL fields before output.
    Affected if User profile URL fields are rendered in badge widgets without proper escaping functions

Your environment is affected if UsersWP is installed with a vulnerable version, badge widgets are in use, and user profile URL fields are not properly escaped when rendered, allowing injected scripts to execute.

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 UsersWP to the latest version which includes proper input sanitization and output escaping for URL fields in badge widgets. If no update is available, implement sanitization (esc_url()) and output escaping (esc_html()/esc_attr()) on all user profile URL fields before rendering.

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-5742 — 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-5742 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