dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-46608

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 WPDO DoLogin Security dologin allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects DoLogin Security: from n/a through <= 3.7.1.

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 missing authorization vulnerability in the WPDO DoLogin Security WordPress plugin (versions through 3.7.1). The plugin has incorrectly configured access control security levels, allowing unauthenticated or improperly authenticated users to potentially bypass authorization checks and access restricted functionality.

MitigationUpdate WPDO DoLogin Security to the latest version beyond 3.7.1 to obtain the patched version with proper authorization controls. If immediate update is not possible, review access control configurations and restrict sensitive endpoints to appropriate user roles.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 WPDO DoLogin Security plugin is installed
    Navigate to WordPress admin dashboard > Plugins page and look for 'WPDO DoLogin Security' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder containing 'dologin' or 'wpdo' in the name
    Affected if The plugin is present in the installation
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WPDO DoLogin Security and note the version number displayed beneath the plugin name, or open the plugin's main PHP file and check the 'Version' header in the plugin comment block
    Affected if The version shown is 3.7.1 or lower (the vulnerability affects versions through 3.7.1)
  3. Check for unauthorized access to restricted features
    Review the plugin settings and examine server access logs for requests to plugin admin URLs or sensitive actions (such as /wp-admin/admin-ajax.php?action=... or plugin-specific endpoints) that originate from unauthenticated users or users lacking proper privileges
    Affected if Unauthenticated or low-privilege users can access plugin administrative functions or sensitive actions that should require higher authorization levels

A user is affected if the WPDO DoLogin Security plugin version is 3.7.1 or lower and unauthenticated or improperly authenticated users can access restricted plugin functionality.

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 WPDO DoLogin Security to the latest version beyond 3.7.1 to obtain the patched version with proper authorization controls. If immediate update is not possible, review access control configurations and restrict sensitive endpoints to appropriate user roles.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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