dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57353

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 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
Subscriber Broken Access Control in Link Whisper Premium <= 2.9.0 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 · moderate confidence

This is a broken access control vulnerability in the Link Whisper Premium WordPress plugin where subscriber-level users (the lowest privilege role) can access functionality or data that should be restricted to higher-privileged users like administrators. The CVSS 6.5 indicates significant impact from unauthorized access to privileged operations.

MitigationUpdate Link Whisper Premium to a version newer than 2.9.0, or apply any available security patches. If immediate update is not possible, consider restricting subscriber registration or monitoring user activity.

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Link Whisper Premium is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Link Whisper Premium' in the list
    Affected if Link Whisper Premium plugin appears in the installed plugins list
  2. Check installed version number
    Click 'View details' on the Link Whisper Premium plugin in the plugins list, or check the plugin header in /wp-content/plugins/link-whisper-premium/ folder for the Version field
    Affected if The displayed version is 2.9.0 or any version lower than 2.9.0
  3. Confirm plugin is active
    In Plugins > Instored Plugins, verify that Link Whisper Premium shows as 'Active' under the plugin name
    Affected if The plugin is currently active and the version is 2.9.0 or lower
  4. Identify subscriber-level users
    Go to Users in WordPress admin and filter or search for users with the 'Subscriber' role
    Affected if There is at least one user account with Subscriber role in the system
  5. Compare version against affected range
    Cross-reference the installed version found in step 2 against the affected range: versions up to and including 2.9.0 are vulnerable
    Affected if Installed version is 2.9.0 or any earlier version, indicating the broken access control vulnerability is present

A user is affected if Link Whisper Premium version 2.9.0 or earlier is installed and active on the WordPress site, especially when subscriber-level accounts exist.

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 Link Whisper Premium to a version newer than 2.9.0, or apply any available security patches. If immediate update is not possible, consider restricting subscriber registration or monitoring user activity.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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