Cyber Resilience

CVE-2025-3607

Published
24 April 2025
Modified
17 June 2026
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0043 35th percentile
Risk Priority 64 floored blend · peak EPSS

Summary

CVE-2025-3607 is a high-severity Unverified Password Change (CWE-620) vulnerability in Wordpress (inferred from references). Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Manipulation (T1098); ranked at the 35th 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 IA-11 (Re-authentication) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

The Frontend Login and Registration Blocks plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.0.8. This is due to the plugin not properly validating a user's identity prior to updating…

more

a password. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

CWE(s)
CWE-620

Related Threats

MITRE ATT&CK Enterprise Techniques

T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
attack.mitre.org →
T1098.001 Additional Cloud Credentials Persistence
Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-12824Shared CWE-620
CVE-2024-47784Shared CWE-620
CVE-2025-3603Shared CWE-620
CVE-2026-40588Shared CWE-620
CVE-2023-4381Shared CWE-620
CVE-2024-27715Shared CWE-620
CVE-2025-63362Shared CWE-620
CVE-2026-44733Shared CWE-620
CVE-2025-61132Shared CWE-620
CVE-2025-14751Shared CWE-620

Affected Assets

Wordpress
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

IA-11 Re-authentication good match

Re-authentication explicitly requires users to prove identity before performing sensitive actions such as password changes.

IA-5 Authenticator Management good match

Authenticator management requires identity verification during password distribution and changes, directly stopping unverified password updates.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.AA-01 mostly match
prevents

Credential management practices directly enforce re-authentication for password changes.

PR.AA-03 mostly match
prevents

Authentication requirements include verifying identity before allowing credential modifications.

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.

A.5.17 Authentication information partial match
degrades

Requires secure management of authentication information, directly addressing the need to verify the original password before allowing a change.

A.8.5 Secure authentication partial match
prevents

Mandates secure authentication mechanisms, which include verifying existing credentials before permitting password changes.

A.5.16 Identity management none match
none

Identity management processes can incorporate verification steps, but the control itself does not explicitly require password-change verification.

A.8.3 Information access restriction none match
none

Information access restriction can be strengthened by password verification, yet the control focuses on access rights rather than change procedures.

References