dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-46485

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-24
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 Carlo La Pera WP Customize Login Page wp-customize-login-page allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WP Customize Login Page: from n/a through <= 1.6.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 · moderate confidence

The WP Customize Login Page plugin <= 1.6.5 contains a missing authorization vulnerability where certain functionality is not properly constrained by access control lists (ACLs). This allows users to access sensitive functionality without proper capability checks, potentially enabling unauthenticated or lower-privileged users to modify login page settings.

MitigationUpdate the WP Customize Login Page plugin to the latest version once available. If no patched version exists, disable the plugin and implement server-level access restrictions or alternative authentication solutions until a fix is released.

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 plugin installation and activation status
    Check if the WP Customize Login Page plugin is installed in your WordPress environment. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and look for 'WP Customize Login Page' in the list. Note whether it is currently activated or deactivated.
    Affected if The plugin is installed and activated on the WordPress site
  2. Identify installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the WP Customize Login Page plugin and locate the version number displayed below the plugin name. Alternatively, check the plugin main PHP file (e.g., wp-content/plugins/customize-login-page/customize-login-page.php) and look for the 'Version' header in the file comment block.
    Affected if The installed version is 1.6.5 or any earlier version
  3. Check for unauthenticated AJAX endpoints
    Inspect the plugin directory for AJAX action handlers. Look in the main plugin file and any included files for do_action('wp_ajax_') or do_action('wp_ajax_nopriv_') calls that handle login page customization settings. These endpoints may be accessible without authentication if nopriv hooks exist.
    Affected if AJAX actions handling login page settings are accessible to unauthenticated users (wp_ajax_nopriv_ hooks present)
  4. Review capability checks on admin actions
    Examine the plugin PHP files for capability checks before modifying settings. Look for current_user_can() or similar WordPress authorization functions before any save/update operations on login page configurations.
    Affected if No capability checks or weak capability checks (e.g., only check for logged-in users without verifying administrative privileges) are found before sensitive operations

You are affected if the WP Customize Login Page plugin is installed and activated at version 1.6.5 or earlier, and the plugin lacks proper capability checks on sensitive functionality accessible to unauthenticated or low-privileged 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP Customize Login Page plugin to the latest version once available. If no patched version exists, disable the plugin and implement server-level access restrictions or alternative authentication solutions until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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