Security Resilience

CVE-2025-14975

Published
29 January 2026
Modified
15 April 2026
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0034 26th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-14975 is a high-severity Improper Privilege Management (CWE-269) vulnerability. Its CVSS base score is 8.1 (High).

Operationally, ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-2 (Account Management) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-14975 is a high-severity vulnerability in the Custom Login Page Customizer WordPress plugin, affecting versions prior to 2.5.4. It arises from an improper password reset process (CWE-269), which fails to enforce adequate authentication checks. Published on 2026-01-29, the issue carries a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), highlighting significant confidentiality, integrity, and availability impacts.

Unauthenticated attackers can exploit this vulnerability remotely if they know a target user's username, such as an administrator's. By sending a few unauthenticated requests, they can reset the password and gain full access to the account, potentially allowing site takeover, data exfiltration, or further compromise of the WordPress installation.

The WPScan advisory at https://wpscan.com/vulnerability/a1403186-51aa-4eae-a3fe-0c559570eb93/ details the issue, with mitigation achieved by updating to version 2.5.4 or later, which addresses the flawed reset mechanism.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Custom Login Page Customizer WordPress plugin before 2.5.4 does not have a proper password reset process, allowing a few unauthenticated requests to reset the password of any user by knowing their username, such as administrator ones, and therefore gain…

more

access to their account

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-21888Shared CWE-269
CVE-2024-29210Shared CWE-269
CVE-2026-83293Shared CWE-269
CVE-2024-34370Shared CWE-269
CVE-2025-67792Shared CWE-269
CVE-2025-59514Shared CWE-269
CVE-2026-72829Shared CWE-269
CVE-2024-8100Shared CWE-269
CVE-2026-18249Shared CWE-269
CVE-2024-42050Shared CWE-269

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.

Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.

Access enforcement applies the correct privilege checks at every request, structurally preventing unintended spheres of control.

Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.

Least privilege is the direct countermeasure to improper privilege management; implementing it eliminates the root cause.

Binding security attributes to subjects/objects supplies the mechanism needed to track and enforce privileges correctly.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.15 directly mandates determining access requirements, defining/enforcing topic-specific access control policy, assigning rights/restrictions by entity/role, consistency with classification, need-to-know, privileged access restrictions, segregation, formal authorization, and dynamic rules — which stops most improper privilege management from being exploitable; bounded remainder is flawed implementation of those rules (e.g. incorrect mapping or enforcement bugs).

blocks

A.5.18 directly governs the provisioning, review, modification and timely revocation of access rights (including for role changes, termination and privilege levels), which stops most improper privilege spheres from being exploitable even if the assignment flaw exists; the bounded remainder is flaws in the underlying enforcement mechanism itself (e.g. AC-3/A.8.3)

blocks

A.8.2 directly controls the identification, allocation, review, expiry, temporary use, and separation of privileged rights per policy, which prevents most improper privilege management (CWE-269) by design; the bounded remainder is flawed tracking/checking logic inside the product's own enforcement code (the AC-3 slice of 269).

blocks

A.8.3 directly restricts access per policies (config mechanisms, per-user/group rights, isolation, dynamic techniques, auth/credential enforcement), which stops exploitation of most improper privilege management cases even if the assignment/tracking flaw remains; named remainder exists for non-access-control privilege errors (e.g. pure assignment bugs outside enforcement).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References