dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25408

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in PluginRx Broken Link Notifier broken-link-notifier allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Broken Link Notifier: from n/a through <= 1.3.5.

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

Missing Authorization vulnerability in the PluginRx Broken Link Notifier WordPress plugin allows unauthorized access due to incorrectly configured access control security levels. The vulnerability exists in versions up to and including 1.3.5, potentially allowing attackers to bypass authorization checks for plugin functionality.

MitigationUpdate the Broken Link Notifier plugin to the latest version beyond 1.3.5 once available, or implement application-level access controls to restrict plugin functions to authenticated users with appropriate privileges.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Broken Link Notifier plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named broken-link-notifier or pluginrx-broken-link-notifier, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The PluginRx Broken Link Notifier plugin files exist in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically broken-link-notifier.php) in the plugin folder and locate the Version header in the plugin comment block, or check the version column in WordPress admin plugins list
    Affected if The reported version is 1.3.5 or any version up to and including 1.3.5
  3. Confirm the plugin is active
    Check the WordPress database wp_options table for active_plugins option containing the plugin, or verify the plugin shows as Active in WordPress admin under Plugins
    Affected if The plugin is activated on the WordPress site

User is affected if the PluginRx Broken Link Notifier plugin is installed, active, and the version is 1.3.5 or lower, allowing unauthorized access to plugin functionality due to missing authorization checks.

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 the Broken Link Notifier plugin to the latest version beyond 1.3.5 once available, or implement application-level access controls to restrict plugin functions to authenticated users with appropriate privileges.

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