CVE-2025-49902
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 · uneditedMissing Authorization vulnerability in A WP Life Login Page Customizer – Customizer Login Page, Admin Page, Custom Design customizer-login-page allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Login Page Customizer – Customizer Login Page, Admin Page, Custom Design: from n/a through <= 2.1.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 confidenceThe customizer-login-page WordPress plugin has a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This broken access control issue permits unauthenticated or lower-privileged users to access sensitive functionality or data that should be restricted to administrators.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck if the customizer-login-page plugin is installed in your WordPress environment by inspecting the wp-content/plugins/ directory or viewing the Plugins page in the WordPress admin dashboard.Affected if The plugin is installed and active in WordPress.
-
Identify installed versionLocate the plugin main file (usually customizer-login-page.php) and check the version declared in the plugin header comment, or query the wp_options table for the option_name containing the plugin version.Affected if The installed version matches any affected version range of the customizer-login-page plugin.
-
Inspect admin access controlsReview the plugin source code for functions handling admin actions, settings pages, or sensitive data. Search for capability checks like current_user_can(), admin_init hooks, or authorization logic on sensitive AJAX endpoints.Affected if Sensitive functions or admin pages lack proper capability checks (e.g., missing current_user_can('manage_options') or similar authorization logic).
-
Test unauthorized accessAttempt to access plugin admin pages or trigger sensitive functions while logged in as a subscriber or unauthenticated user. Check if lower-privileged accounts can modify plugin settings or access admin-only functionality.Affected if Unauthenticated or lower-privileged users (e.g., subscriber role) can access or modify plugin settings or sensitive functionality that should require administrator privileges.
If the customizer-login-page plugin is installed and its sensitive functions or admin pages lack proper authorization checks allowing unauthenticated or low-privilege access, the environment is affected by CVE-2025-49902.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks and capability verification on all sensitive functions and admin pages. Update to the latest patched version when available and limit admin access to trusted personnel only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-49902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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