VulnerabilityPublished 22 Feb 2026Updated 23 Feb 2026

CVE-2026-2898: funadmin · Deserialization

Affects funadminSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
funadmin	Affected 7.1.0-rc1 – 7.1.0-rc4 4 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:funadmin:funadmin:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2898, organizations should first identify all instances of funadmin running affected versions (7.1.0-rc1 to 7.1.0-rc4) and isolate them from untrusted networks where possible. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious deserialization payloads targeting the cloud_account parameter. 3) Implement input validation and sanitization at the application layer to reject malformed or unexpected serialized data. 4) Monitor logs for unusual activity related to deserialization or cloud_account parameter usage. 5) Consider upgrading to a newer, unaffected version of funadmin once available or applying community-developed patches if trustworthy. 6) Conduct security reviews and code audits focusing on deserialization usage throughout the application to prevent similar issues. 7) Educate developers about secure deserialization practices and the risks of accepting untrusted serialized input. These targeted actions will reduce the attack surface and help prevent exploitation until an official fix is released.

Description

A vulnerability was detected in funadmin up to 7.1.0-rc4. This issue affects the function getMember of the file app/common/service/AuthCloudService.php of the component Backend Endpoint. The manipulation of the argument cloud_account results in deserialization. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The impact of CVE-2026-2898 on organizations using funadmin can be significant if exploited. Successful exploitation could allow attackers to execute arbitrary code remotely, leading to potential data breaches, unauthorized access to sensitive backend systems, and disruption of services. The vulnerability affects confidentiality by exposing sensitive member or cloud account information, integrity by allowing manipulation of backend processes, and availability by potentially causing service interruptions or crashes. Although the CVSS score is medium, the presence of a public exploit increases the risk of targeted attacks, especially in environments where funadmin is used to manage critical backend operations. Organizations relying on affected versions may face operational disruptions, reputational damage, and compliance issues if the vulnerability is exploited. The lack of vendor response and patches further elevates the risk, necessitating proactive mitigation.

Summary

CVE-2026-2898 is a deserialization vulnerability identified in the funadmin backend management system, specifically in versions 7.1.0-rc1 through 7.1.0-rc4. The vulnerability resides in the getMember function of the AuthCloudService.php file, where the cloud_account parameter is deserialized without proper validation or sanitization. This unsafe deserialization can be exploited remotely by an attacker who crafts malicious input to manipulate the deserialization process, potentially leading to arbitrary code execution or unauthorized access. The vulnerability does not require prior authentication but does require some form of user interaction, such as triggering the vulnerable function remotely. The CVSS 4.0 base score is 5.1, reflecting medium severity due to the limited impact on confidentiality, integrity, and availability, combined with the ease of remote exploitation but requiring user interaction. The vendor has not issued a patch or responded to disclosure efforts, and while a public exploit exists, no confirmed exploitation in the wild has been reported. This vulnerability highlights the risks of unsafe deserialization in web applications and backend services, emphasizing the need for secure coding practices and input validation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 1 Mar 2026, 06:17 UTC

Public exploits and detectionGitHub proofs of concept

Technical details

References

Community reviews

Related threats