dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-46082

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-02
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 Cyberlord92 Broken Link Checker | Finder broken-link-finder allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Broken Link Checker | Finder: from n/a through <= 2.4.2.

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

The Broken Link Checker | Finder WordPress plugin versions up to 2.4.2 contains a missing authorization vulnerability where the plugin fails to properly enforce access control checks on certain functionality. This allows attackers to exploit incorrectly configured security levels, potentially allowing unauthenticated or lower-privileged users to access administrative features intended for higher-privileged users.

MitigationImplement proper capability checks (such as current_user_can()) on all sensitive plugin functions and admin actions to enforce WordPress role-based access control. Verify all AJAX handlers and admin pages validate user permissions before executing privileged operations.

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. Check plugin version installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Broken Link Checker | Finder' and verify the version number displayed. Alternatively, inspect the main plugin file (typically broken-link-checker.php or similar in wp-content/plugins/) and look for a 'Version:' comment or constant definition.
    Affected if The installed version is 2.4.2 or any earlier version (e.g., 2.4.1, 2.4.0, etc.)
  2. Identify AJAX handlers lacking capability checks
    Examine the main plugin PHP file and any included files for AJAX action hooks (wp_ajax_*, wp_ajax_nopriv_*) and verify if each handler includes a current_user_can() or similar capability verification call before executing sensitive operations.
    Affected if Any AJAX handler processes requests without first validating user permissions (e.g., missing current_user_can('manage_options') or similar privilege checks)
  3. Inspect admin page handlers for authorization
    Review admin menu registration callbacks and admin page template files for functions that perform privileged operations (such as database writes, settings modifications, or bulk actions) and confirm they include capability checks.
    Affected if Admin functions execute privileged operations without verifying the user has the appropriate WordPress capability (administrator-level or similar)
  4. Review action and filter hooks for missing authorization
    Search plugin source code for action hooks (do_action) and filter hooks (apply_filters) that modify WordPress data, add links to admin menus, or process form submissions, and verify each calls current_user_can() before proceeding.
    Affected if Any action or filter hook performs administrative actions without validating user capabilities first

A user is affected if the installed plugin version is 2.4.2 or earlier AND the plugin contains AJAX handlers, admin pages, or other functions that process requests without verifying user capabilities.

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

Implement proper capability checks (such as current_user_can()) on all sensitive plugin functions and admin actions to enforce WordPress role-based access control. Verify all AJAX handlers and admin pages validate user permissions before executing privileged operations.

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-2023-46082 — 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-2023-46082 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