CVE-2026-2896

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to bypass authorization controls in funadmin's configuration handler, potentially enabling unauthorized configuration changes. It affects funadmin installations up to version 7.1.0-rc4. The exploit is publicly available and can be executed remotely without authentication.

💻 Affected Systems

Products:
  • funadmin
Versions: Up to and including 7.1.0-rc4
Operating Systems: All platforms running funadmin
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the Configuration Handler component via app/backend/controller/Ajax.php setConfig function

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise through unauthorized configuration changes leading to privilege escalation, data exposure, or remote code execution.

🟠

Likely Case

Unauthorized configuration modifications allowing attackers to alter system settings, disable security controls, or gain administrative access.

🟢

If Mitigated

Limited impact with proper network segmentation, strong authentication, and configuration monitoring in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit code is publicly available on GitHub and vuldb, making attacks easy to execute

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider upgrading to any version beyond 7.1.0-rc4 if released, or implement workarounds.

🔧 Temporary Workarounds

Restrict Access to Ajax.php

all

Block or restrict access to the vulnerable Ajax.php file via web server configuration or firewall rules

# Apache: <LocationMatch "^/app/backend/controller/Ajax\.php"> Require all denied </LocationMatch>
# Nginx: location ~ ^/app/backend/controller/Ajax\.php { deny all; }

Implement Web Application Firewall

all

Deploy WAF rules to block requests targeting the setConfig function in Ajax.php

# Example ModSecurity rule: SecRule REQUEST_URI "@rx /app/backend/controller/Ajax\.php.*setConfig" "id:1001,phase:1,deny"

🧯 If You Can't Patch

  • Isolate funadmin instances behind network segmentation with strict access controls
  • Implement comprehensive logging and monitoring for configuration changes and unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Check funadmin version. If version is 7.1.0-rc4 or earlier, system is vulnerable. Also check if Ajax.php setConfig function is accessible without proper authorization.

Check Version:

Check funadmin configuration files or admin panel for version information

Verify Fix Applied:

Test if unauthorized requests to /app/backend/controller/Ajax.php with setConfig parameter are properly blocked or require authentication.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized POST requests to /app/backend/controller/Ajax.php with setConfig parameter
  • Configuration changes from unexpected IP addresses or users

Network Indicators:

  • HTTP requests to Ajax.php endpoint without proper authentication headers
  • Unusual traffic patterns to backend controller paths

SIEM Query:

source="web_server" AND (uri="/app/backend/controller/Ajax.php" AND method="POST" AND params CONTAINS "setConfig")

🔗 References

📤 Share & Export