CVE-2026-28674

xiaoheiFS is a self-hosted financial and operational system for cloud service businesses.

Verified by Precogs Threat Research
Last Updated: Mar 18, 2026
Base Score
7.2HIGH

Executive Summary

CVE-2026-28674 is a high severity vulnerability affecting appsec, pii-secrets, binary-analysis. It is classified as Unrestricted Upload. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.

Precogs AI Insight

"Architecturally, this flaw occurs due to within XiaoheiFS, allowing bypassed validation checks on external interactions. When targeted, an adversary might use this to seize control of the underlying infrastructure and pivot to adjacent networks. Precogs AI Analysis Engine utilizes semantic code analysis to identify exploitable weaknesses before attackers do."

Exploit Probability (EPSS)
Low (0.1%)
Public POC
Undisclosed
Exploit Probability
Elevated (52%)
Public POC
Available
Affected Assets
appsecpii secretsbinary analysisCWE-434

What is this vulnerability?

CVE-2026-28674 is categorized as a critical Application Verification Flaw flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.

xiaoheiFS is a self-hosted financial and operational system for cloud service businesses. In versions up to and including 0.3.15, the `AdminPaymentPluginUp...

This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.

Risk Assessment

MetricValue
CVSS Base Score7.2 (HIGH)
Vector StringCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
PublishedMarch 18, 2026
Last ModifiedMarch 18, 2026
Related CWEsCWE-434, CWE-798

Impact on Systems

Unauthorized Access: Flaws in application logic can permit unauthorized interaction with protected APIs.

Data Manipulation: Adversaries may alter critical application states, such as user roles or configurations.

Service Disruption: Improper error handling or unvalidated inputs can lead to resource exhaustion.

How to fix this issue?

Implement the following strategic mitigations immediately to eliminate the attack surface.

1. Defense in Depth Implement multi-layered validation (client-side, API gateway, and server-side).

2. Least Privilege Ensure backend service accounts operate with the absolute minimum rights required.

3. Security Regression Testing Integrate automated semantic security scanning into the deployment pipeline.

Vulnerability Signature

// Generic Application Security Flaw (Node.js)
app.post('/api/update-profile', (req, res) =\> \{
    // DANGEROUS: Mass Assignment / Object Injection
    // Attacker can pass \{ "isAdmin": true, "email": "..." \}
    User.update(\{ id: req.user.id \}, req.body);
    
    // SECURED: Explicitly select permitted fields
    const \{ email, displayName, bio \} = req.body;
    User.update(\{ id: req.user.id \}, \{ email, displayName, bio \});
\});

References and Sources

Vulnerability Code Signature

Attack Data Flow

StageDetail
SourceUser-uploaded file
VectorFile is saved to a web-accessible directory without validation
SinkFile system write operation
ImpactRemote Code Execution (RCE), full system compromise

Vulnerable Code Pattern

// ❌ VULNERABLE: Unrestricted Upload
$target_dir = "uploads/";
$target_file = $target_dir . basename($_FILES["fileToUpload"]["name"]);
// Taint sink: saving file without extension/type validation
move_uploaded_file($_FILES["fileToUpload"]["tmp_name"], $target_file);

Secure Code Pattern

// ✅ SECURE: Validated Upload
$target_dir = "uploads/";
$filename = basename($_FILES["fileToUpload"]["name"]);
$filetype = strtolower(pathinfo($filename, PATHINFO_EXTENSION));

// Sanitized validation: strict allowlist
$allowed_types = array("jpg", "png", "gif");
if (in_array($filetype, $allowed_types)) {
    // Generate safe unique filename
    $safe_filename = uniqid() . "." . $filetype;
    move_uploaded_file($_FILES["fileToUpload"]["tmp_name"], $target_dir . $safe_filename);
}

How Precogs Detects This

Precogs AI Analysis Engine utilizes semantic taint tracking to detect insecure file upload routines and missing extension validation.\n

Related Vulnerabilitiesvia CWE-434

Is your system affected?

Precogs AI detects CVE-2026-28674 in compiled binaries, LLMs, and application layers — even without source code access.