Cyber Resilience

CVE-2023-4214

Auth Bypass in Apppresser ≤ 4.3.0

Published
18 November 2023
Modified
08 April 2026
Patch / advisory
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.0092 57th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2023-4214 is a high-severity Unverified Password Change (CWE-620) vulnerability in Apppresser Apppresser. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Manipulation (T1098); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The AppPresser plugin for WordPress is vulnerable to unauthorized password resets in versions up to, and including 4.2.5. This is due to the plugin generating too weak a reset code, and the code used to reset the password has no…

more

attempt or time limit.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
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.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9305Same product: Apppresser Apppresser
CVE-2024-31268Same product: Apppresser Apppresser
CVE-2025-1561Same product: Apppresser Apppresser
CVE-2024-31374Same product: Apppresser Apppresser
CVE-2024-4611Same product: Apppresser Apppresser
CVE-2024-11024Same product: Apppresser Apppresser
CVE-2024-32776Same product: Apppresser Apppresser
CVE-2025-4552Shared CWE-620, CWE-640
CVE-2026-2543Shared CWE-620, CWE-640
CVE-2025-6097Shared CWE-620, CWE-640

Affected Assets

apppresser
apppresser
≤ 4.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V7.4.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-640

Establishing procedures for lost or compromised authenticators addresses weak password recovery mechanisms.

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-02 mostly match
prevents

Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.

PR.AA-03 mostly match
prevents

Authentication requirements include verifying identity before allowing credential modifications.

PR.PS-06 partial match
prevents

Secure SDLC reduces implementation flaws but is not specific to password-recovery design.

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.

degrades

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

prevents

Secure-SDLC practices can embed strong recovery design, yet the control is broader than this single weakness.

prevents

Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.

prevents

Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.

prevents

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

none

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

References