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

CVE-2026-5506

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
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 Wavr plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `wave` shortcode in all versions up to, and including, 0.2.6. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected 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 confidence

The Wavr WordPress plugin (versions up to 0.2.6) contains a stored XSS vulnerability in its `wave` shortcode due to insufficient input sanitization and missing output escaping on user-supplied attributes. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript through shortcode parameters, which executes when users view affected pages.

MitigationUpdate the Wavr plugin to a version beyond 0.2.6 that implements proper input sanitization and output escaping for shortcode attributes. Until then, limit contributor-level access and audit existing content using the wave shortcode.

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 Wavr plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Wavr' in the list of active or inactive plugins
    Affected if Wavr plugin appears in the plugins list and is active or inactive on the site
  2. Check installed Wavr version
    In the Plugins list, click on 'Wavr' to view the plugin details, or check the plugin files in wp-content/plugins/wavr/ for a version file or readme.txt containing the version number
    Affected if The installed version is 0.2.6 or any version prior to the fixed release
  3. Identify use of wave shortcode
    Search the WordPress database or content for instances of [wave] shortcode by querying wp_posts for post_content containing 'wave' shortcode, or use a site search for the shortcode pattern
    Affected if Any posts, pages, or custom post types contain the [wave] shortcode
  4. Inspect shortcode attributes for lack of sanitization
    Examine the plugin source code in wavr.php or related files to locate the shortcode handler function and verify whether sanitize_text_field(), esc_attr(), or esc_html() are applied to shortcode attributes before output
    Affected if The shortcode handler outputs attributes without proper sanitization and escaping functions
  5. Verify contributor-level user access exists
    Check WordPress user roles under Users > All Users to see if any accounts have the Contributor role or higher, which allows shortcode usage in post content
    Affected if At least one user account with Contributor-level access or higher exists on the site

A site is affected if the Wavr plugin version is 0.2.6 or earlier, the wave shortcode is in use, and any user with Contributor access or higher exists on the WordPress site.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Wavr plugin to a version beyond 0.2.6 that implements proper input sanitization and output escaping for shortcode attributes. Until then, limit contributor-level access and audit existing content using the wave shortcode.

Recommended fix Moderate confidence

Wavr plugin version 0.2.7 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Wavr plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version of the Wavr plugin from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the wave shortcode functionality still works as expected
  7. 7. Test that the fix properly sanitizes input in the wave shortcode attributes

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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