Cyber Resilience

CVE-2026-2895

Auth Bypass in Funadmin ≤ 7.1.0

Public PoCAuth Bypass
Published
21 February 2026
Modified
24 February 2026
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0039 32th percentile
Risk Priority 31 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-2026-2895 is a medium-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Funadmin Funadmin. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to IA-12 (Identity Proofing) and IA-5 (Authenticator Management) — 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-2026-2895 is a security vulnerability in funadmin versions up to 7.1.0-rc4, specifically affecting the repass function in the file app/frontend/controller/Member.php. The flaw enables weak password recovery through manipulation of the forget_code or vercode arguments, classified under CWE-640. It carries a CVSS v3.1 base score of 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N), indicating low severity with network accessibility but high attack complexity.

Remote attackers require no privileges to attempt exploitation, though the high complexity makes it difficult to execute successfully. Exploitation leads to a low-impact integrity violation, allowing weak password recovery that could compromise user account security by bypassing robust recovery controls.

Advisories note that the vendor was contacted early about the disclosure but provided no response, with no patches or official mitigations available. References include GitHub issues at https://github.com/I4m6da/CVE/issues/2 and related comments, as well as VulDB entries at https://vuldb.com/?ctiid.347206, https://vuldb.com/?id.347206, and https://vuldb.com/?submit.753971, which confirm the issue details.

The exploit has been publicly released and may be used for attacks, though exploitation remains known to be difficult. The vulnerability was published on 2026-02-21.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A security flaw has been discovered in funadmin up to 7.1.0-rc4. Affected by this issue is the function repass of the file app/frontend/controller/Member.php. Performing a manipulation of the argument forget_code/vercode results in weak password recovery. Remote exploitation of the attack…

more

is possible. The attack's complexity is rated as high. The exploitation is known to be difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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-2026-2896Same product: Funadmin Funadmin
CVE-2026-2894Same product: Funadmin Funadmin
CVE-2023-24782Same product: Funadmin Funadmin
CVE-2023-2477Same product: Funadmin Funadmin
CVE-2024-48228Same product: Funadmin Funadmin
CVE-2024-48227Same product: Funadmin Funadmin
CVE-2023-24777Same product: Funadmin Funadmin
CVE-2023-24780Same product: Funadmin Funadmin
CVE-2024-48218Same product: Funadmin Funadmin
CVE-2024-48231Same product: Funadmin Funadmin

Affected Assets

funadmin
funadmin
7.1.0 · ≤ 7.1.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

Mitigating Controls (NIST 800-53 r5) AI

Identity proofing at appropriate assurance levels ensures forgotten-password recovery cannot succeed without strong verification of the user.

Authenticator management requires secure distribution, reset, and verification procedures that directly address weak password recovery flows.

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 lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
prevents

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

PR.AA-03 partial match
prevents

Authentication policy covers strength/MFA but does not address recovery path weaknesses.

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

Strong authentication-information lifecycle rules directly address weak password-recovery flows.

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.

mitigates

Secure-authentication requirements include robust forgotten-password procedures.

References