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

CVE-2026-57333

HIGH · 7.1 CVSS v3.1 Developing Published 2026-06-29
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 7 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
Unauthenticated Cross Site Scripting (XSS) in Link Whisper Free <= 0.9.4 versions.

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 · low confidence

Unauthenticated Cross Site Scripting (XSS) vulnerability in Link Whisper Free plugin for WordPress, affecting versions 0.9.4 and below. An attacker can inject malicious scripts without authentication, likely through unsanitized user input in the plugin's frontend or admin interfaces.

MitigationUpdate Link Whisper Free to a version newer than 0.9.4 when a patch is available. If no patched version exists, remove the plugin or implement web application firewall rules to block XSS attack patterns.

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. Confirm Link Whisper Free is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Link Whisper Free' in the list.
    Affected if The plugin appears in the installed plugins list and is activated
  2. Identify the installed version
    In the plugins list, click 'View Details' under Link Whisper Free or view the plugin file header in wp-content/plugins/link-whisper-free/ directory to find the version number.
    Affected if The version number displayed is 0.9.4 or lower (for example, 0.9.4, 0.9.3, 0.9.2, etc.)
  3. Check if the plugin exposes input fields to unauthenticated users
    Inspect the frontend of the site or the plugin admin pages while logged out. Look for any Link Whisper-related forms, search fields, or URL parameters that could accept user input without authentication.
    Affected if Any Link Whisper input fields or parameters are accessible without logging in
  4. Review for existing script injection
    View the page source of your WordPress site frontend, check browser console for unexpected errors, and review server access logs for common XSS payload patterns (such as <script>, onerror=, onload=, javascript:).
    Affected if Malicious JavaScript code appears in page source or logs contain XSS probe requests

You are affected if Link Whisper Free is installed with version 0.9.4 or below and the vulnerable input points are accessible to unauthenticated users.

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 Link Whisper Free to a version newer than 0.9.4 when a patch is available. If no patched version exists, remove the plugin or implement web application firewall rules to block XSS attack patterns.

Recommended fix Moderate confidence

Link Whisper Free version greater than 0.9.4 (check wordpress.org for latest release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find Link Whisper Free plugin
  4. Check if the current version is 0.9.4 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the patch

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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